Description of problem: Cloning some PVC gets wrong size Version-Release number of selected component (if applicable): How reproducible: Always Steps to Reproduce: 1.Get in storage and choose PesistentVolumeClaims. 2.Clone one of PVCs. 3.The size of clone PVC is wrong. Actual results: Expected results: The same size as the original PVC. Additional info:
Hi Shijie, could you, please, add more info about this bug? What exactly did you mean by "Get in storage"? Or could you maybe add some screenshot of the location of the problem? Is the problem occurring in some screen placed under "Virtualization" menu item? Thanks!
Hi Hilda, Sorry for the confusion. Here are some screenshots: https://docs.google.com/document/d/1NkjCLUZRr2u_xywAdxusvjkRrjMyJfYoiMAilt1i1M4/edit?usp=sharing @hstastna
Thank you for the screenshots, Shijie. Seems to me that it's a bug for Storage team, we are Virtualization team (see Virtualization in the menu). Guohua, could you help us to point this BZ to the right team? Thanks!
It seems the issue only happens for certain PVCs, like PVC for dataSource in ns openshift-virtualization-os-images and PVCs for VMs, If nothing can be done from our side, we can close the bug and move the Jira issue to OCP.
Guohua, PersistentVolumeClaims page is simply not included in our kubevirt-plugin repo (or older console repo). However I am not sure which team that part of the UI belongs to.
(In reply to Hilda Stastna from comment #5) > Guohua, PersistentVolumeClaims page is simply not included in our > kubevirt-plugin repo (or older console repo). > However I am not sure which team that part of the UI belongs to. Okay, close the bug for now