vanecka opened a new issue, #14572:
URL: https://github.com/apache/cloudstack/issues/14572

   ### problem
   
   When a VM is owned by a project, selecting the Volumes menu item does not 
display a list of the Volumes attached to the VM. Instead, no results are 
displayed:
   
   <img width="1371" height="900" alt="Image" 
src="https://github.com/user-attachments/assets/ef0d19e2-fe22-4a20-bb5c-fee427327a41";
 />
   
   To find the attached storage, browse to Storage -> Volumes, ensure the 
Project option is activated, increase the number of results displayed to max 
(200), press Ctrl+F to search by Instance name (perhaps a feature to filter by 
instance name would also be helpful), and type the VM name to find its volumes:
   
   <img width="1391" height="523" alt="Image" 
src="https://github.com/user-attachments/assets/23c3ea8d-6f85-49c7-b30b-2f6a5986a5e7";
 />
   
   The same goes for cmk:
   When listing volumes for the VM, nothing is initially returned:
   
   <img width="611" height="56" alt="Image" 
src="https://github.com/user-attachments/assets/6807e30d-3949-495e-8edd-1eb16fee498e";
 />
   
   To see the desired results, one has to specify the Project ID too:
   
   <img width="923" height="158" alt="Image" 
src="https://github.com/user-attachments/assets/f45d58c1-a26b-4af6-a0ab-079d5cdb0df6";
 />
   
   
   ### versions
   
   ACS: 4.23.0.0 (cloudstack-management-4.23.0.0-1.noarch)
   Hypervisor: qemu-kvm-core-10.1.0-16.el10_2.5.x86_64
   Storage: ceph-base-20.2.1-1.el10.x86_64
   Network: Advanced with VLANs, over Mellanox PCIe 2-port 25GbE SFP28
   OS: Rocky Linux 10.2
   
   ### The steps to reproduce the bug
   
   1. Change the ownership of a VM to an existing project
   2. Open the VM
   3. Browse to the Volumes of the VM
   4. No Volumes are listed
   5. To see the attached volumes from this screen, one has to change the 
ownership to a user object, but this may invalidate the networks that the VM 
belongs to.
   
   
   ### What to do about it?
   
   If a VM belongs to a project (projectid <> NULL), use the project ID in the 
API to display the volumes correctly. The UI already "knows" the VM's project 
ID because its name is looked up and displayed under the Project info text.


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: [email protected]

For queries about this service, please contact Infrastructure at:
[email protected]

Reply via email to