Bug 2103807 - PVC is not named by VM name while creating vm quickly
Summary: PVC is not named by VM name while creating vm quickly
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: User Experience
Version: 4.11.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.12.0
Assignee: Hilda Stastna
QA Contact: Guohua Ouyang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-05 01:32 UTC by Guohua Ouyang
Modified: 2023-01-24 13:37 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-01-24 13:37:41 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt-ui kubevirt-plugin pull 761 0 None open Bug 2103807: Name PVC source same as VM name when creating VM quickly 2022-07-15 15:31:17 UTC
Red Hat Issue Tracker CNV-19634 0 None None None 2022-12-15 08:44:19 UTC
Red Hat Product Errata RHSA-2023:0408 0 None None None 2023-01-24 13:37:54 UTC

Description Guohua Ouyang 2022-07-05 01:32:06 UTC 
Description of problem:
Create a vm by the 'quick create virtualmachine' button and then check the vm disk pvc name, it's something like 'rhel9-jtwypptjxwlccd2c', not align with the vm name 'rhel9-corresponding-guanaco'.

If creating the vm via the customize button, no such problem.

Version-Release number of selected component (if applicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:
Comment 1 Guohua Ouyang 2022-07-27 04:49:13 UTC 
verified in v4.12.0-88
Comment 5 errata-xmlrpc 2023-01-24 13:37:41 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (Important: OpenShift Virtualization 4.12.0 Images security update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2023:0408
Note You need to log in before you can comment on or make changes to this bug.