volumes #381

New issue

Open

opened 2026-02-27 15:58:27 +03:00 by kerem · 4 comments

kerem commented

2026-02-27 15:58:27 +03:00

Owner

Originally created by @yinhe1913 on GitHub (Dec 19, 2024).
Original GitHub issue: https://github.com/retspen/webvirtcloud/issues/660

webvirtcloud管理虚拟机时，添加现有磁盘，存储卷为空，看不到已有磁盘问题

无意之间修改了/srv/webvirtcloud/webvirtcloud/settings.py DEBUG = True 问题就解决了，不知道是为啥？请大神们看看

Originally created by @yinhe1913 on GitHub (Dec 19, 2024). Original GitHub issue: https://github.com/retspen/webvirtcloud/issues/660 webvirtcloud管理虚拟机时，添加现有磁盘，存储卷为空，看不到已有磁盘问题 ![存储卷为空问题-1733569010926-2](https://github.com/user-attachments/assets/5bf74f75-8aa5-4055-8cd3-5dd87497bc60) 无意之间修改了/srv/webvirtcloud/webvirtcloud/settings.py DEBUG = True 问题就解决了，不知道是为啥？请大神们看看

kerem commented

2026-02-27 15:58:27 +03:00

Author

Owner

@yinhe1913 commented on GitHub (Feb 24, 2025):

When managing virtual machines with WebVirtCloud, when trying to add an existing disk, the storage volume is empty and the existing disks cannot be seen. By chance, I modified the configuration in /srv/webvirtcloud/webvirtcloud/settings.py by setting DEBUG = True, and the problem was solved. I'm not sure why this happened. Could you experts take a look? Thank you!

@yinhe1913 commented on GitHub (Feb 24, 2025): When managing virtual machines with WebVirtCloud, when trying to add an existing disk, the storage volume is empty and the existing disks cannot be seen. By chance, I modified the configuration in /srv/webvirtcloud/webvirtcloud/settings.py by setting DEBUG = True, and the problem was solved. I'm not sure why this happened. Could you experts take a look? Thank you!

kerem commented

2026-02-27 15:58:27 +03:00

Author

Owner

@ShengruiZhang commented on GitHub (Feb 28, 2025):

这个问题我也遇到过，解决办法也是一样。这个问题里提到过类似的问题，可以参考以下（尽管我觉得并没有解决根本问题） #615

I have also encountered this issue, and it was resolved the same way as yours. Here's another issue that mentions a similar symptom, feel free to check it out (although I don't think the root cause was found) #615

@ShengruiZhang commented on GitHub (Feb 28, 2025): 这个问题我也遇到过，解决办法也是一样。这个问题里提到过类似的问题，可以参考以下（尽管我觉得并没有解决根本问题） #615 I have also encountered this issue, and it was resolved the same way as yours. Here's another issue that mentions a similar symptom, feel free to check it out (although I don't think the root cause was found) #615

kerem commented

2026-02-27 15:58:28 +03:00

Author

Owner

@tmltmltml commented on GitHub (Oct 28, 2025):

It seems that, when create instance, if

DEBUG = True, will result in get "/computes/" + compute_id + "/storage/" + pool + "/volumes/"
DEBUG = False, will result in get "/computes/" + compute_id + "/storage/" + pool + "/volumes"
similar with #615 which is solved in #649 .

So, there is anthoer workaround: modify /volumes to /volumes/ for function get_cust_vols and get_template_vols in instances/templates/create_instance_w2.html.

@tmltmltml commented on GitHub (Oct 28, 2025): It seems that, when create instance, if - DEBUG = True, will result in get `"/computes/" + compute_id + "/storage/" + pool + "/volumes/"` - DEBUG = False, will result in get `"/computes/" + compute_id + "/storage/" + pool + "/volumes"` similar with #615 which is solved in #649 . So, there is anthoer workaround: modify `/volumes` to `/volumes/` for function `get_cust_vols` and `get_template_vols` in `instances/templates/create_instance_w2.html`.

kerem commented

2026-02-27 15:58:28 +03:00

Author

Owner

@qwrty-ftw commented on GitHub (Nov 21, 2025):

Also on my side, DEBUG = True fix the issue.

@retspen

@qwrty-ftw commented on GitHub (Nov 21, 2025): Also on my side, DEBUG = True fix the issue. @retspen