Bug 2046596 - PVC name on customize wizard should match template pvc name
Summary: PVC name on customize wizard should match template pvc name
Keywords:
Status: CLOSED NEXTRELEASE
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Console Kubevirt Plugin
Version: 4.10
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 4.11.0
Assignee: Matan Schatzman
QA Contact: Guohua Ouyang
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-01-27 03:27 UTC by Guohua Ouyang
Modified: 2022-05-11 09:25 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-05-11 09:25:57 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
pvc name should match the template pvc name (2.07 MB, application/octet-stream)
2022-01-27 03:27 UTC, Guohua Ouyang 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Github openshift console pull 10977 0 None Merged Bug 2046596: Customized wizard PVC name 2022-02-10 07:22:40 UTC

Description Guohua Ouyang 2022-01-27 03:27:02 UTC 
Created attachment 1855681 [details]
pvc name should match the template pvc name

Description of problem:
If the template boot source is auto-updated, the name is looking like `rhel9-401cc6250f89`, but the PVC name on customize wizard is 'rhel9' which is not existing.

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

How reproducible:
100%

Steps to Reproduce:
1. check boot source PVC for the template, it something like `rhel9-401cc6250f89`
2. create vm from the template
3. go to customize wizard

Actual results:
it shows 'rhel9'

Expected results:
it shows 'rhel9-401cc6250f89'

Additional info:
Comment 4 Guohua Ouyang 2022-02-11 05:24:31 UTC 
Tested on master, the PVC name is not showing on customize wizard anymore.
Comment 5 Guohua Ouyang 2022-05-11 09:25:57 UTC 
Close the bug as we moved to new UI and this is not a must.
Note You need to log in before you can comment on or make changes to this bug.