Bug 2151766 - "No available boot source" shows while creating VM from existing PVC
Summary: "No available boot source" shows while creating VM from existing PVC
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: User Experience
Version: 4.12.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.13.0
Assignee: Matan Schatzman
QA Contact: Guohua Ouyang
URL:
Whiteboard:
Depends On:
Blocks: 2173482
TreeView+ depends on / blocked
 
Reported: 2022-12-08 05:46 UTC by Guohua Ouyang
Modified: 2023-05-18 02:56 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
: 2173482 (view as bug list)
Environment:
Last Closed: 2023-05-18 02:56:16 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt-ui kubevirt-plugin pull 1066 0 None open Bug 2151766: No boot source available for existing pvc 2023-02-21 11:33:41 UTC
Red Hat Issue Tracker CNV-23253 0 None None None 2022-12-08 05:56:55 UTC
Red Hat Product Errata RHSA-2023:3205 0 None None None 2023-05-18 02:56:27 UTC

Description Guohua Ouyang 2022-12-08 05:46:16 UTC 
Description of problem:
"No available boot source" shows while creating VM from existing PVC

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

How reproducible:
100%

Steps to Reproduce:
1. create a vm from catalog
2. select blank disk
3. edit the disk by using an existing PVC
4. create the VM

Actual results:
"No available boot source" shows 

Expected results:
The VM is created without "No available boot source"

Additional info:
Comment 4 errata-xmlrpc 2023-05-18 02:56:16 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 (Moderate: OpenShift Virtualization 4.13.0 Images security, bug fix, and enhancement 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:3205
Note You need to log in before you can comment on or make changes to this bug.