| Summary: | Could not customize boot source due to source PVC not found | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Guohua Ouyang <gouyang> | ||||||
| Component: | Console Kubevirt Plugin | Assignee: | Aviv Turgeman <aturgema> | ||||||
| Status: | CLOSED ERRATA | QA Contact: | Guohua Ouyang <gouyang> | ||||||
| Severity: | high | Docs Contact: | |||||||
| Priority: | high | ||||||||
| Version: | 4.9 | CC: | aos-bugs, aturgema, gouyang, tnisan, ycui, yzamir | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | 4.10.0 | ||||||||
| Hardware: | Unspecified | ||||||||
| OS: | Unspecified | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | No Doc Update | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2022-03-10 16:05:09 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Attachments: |
|
||||||||
Created attachment 1819625 [details]
screeshot of cannot create vm from customized template
It also cannot create VM from the customized template.
verified on master, now it's able to create customize template from existing customize template. 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 (Moderate: OpenShift Container Platform 4.10.3 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-2022:0056 |
Created attachment 1813028 [details] source PVC not found Description of problem: After customize a boot source for template a and seal it to template b, try to customize the boot source for template b, it could not because of error 'source PVC not found'. This is a very common scenario which should be supported. Version-Release number of selected component (if applicable): master How reproducible: 100% Steps to Reproduce: 1. customize a boot source for template a and seal it to template b 2. try to customize boot source for template b 3. Actual results: Expected results: Additional info: