Bug 2236060 - Upload a DV with WFFC SC via virtctl fails because PVC is pending
Summary: Upload a DV with WFFC SC via virtctl fails because PVC is pending
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Storage
Version: 4.14.0
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: ---
: 4.14.0
Assignee: Álvaro Romero
QA Contact: dalia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-30 09:18 UTC by dalia
Modified: 2023-11-08 14:06 UTC (History)
0 users

Fixed In Version: v4.14.0.rhel9-1913
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-11-08 14:06:16 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt kubevirt pull 10380 0 None Merged Allow image-upload to recover from PendingPopulation phase 2023-09-07 13:13:29 UTC
Github kubevirt kubevirt pull 10397 0 None open [release-1.0] Allow image-upload to recover from PendingPopulation phase 2023-09-07 13:13:31 UTC
Red Hat Issue Tracker CNV-32688 0 None None None 2023-09-06 13:05:56 UTC
Red Hat Product Errata RHSA-2023:6817 0 None None None 2023-11-08 14:06:27 UTC

Description dalia 2023-08-30 09:18:56 UTC
Description of problem:
Previously the order to deploy a VM from a DV uploaded via virtctl with WFFC storage class was:

Upload the the DV -> Deploy A running VM from DV, PVC get bound -> upload the DV again via virtctl


But in 4.14, with the populators, the PVC remain pending after the VM deployment and the upload of the DV fails.

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

How reproducible:
100%

Steps to Reproduce:
1. Upload DV with WFFC storage class
2. Deploy a running VM from the DV
3. Upload DV again

Actual results:
The Upload fails: 
PVC wffc-dv-name not available for upload

Expected results:
Upload succeed and the VM is running 

Additional info:

Comment 1 dalia 2023-09-18 13:53:27 UTC
verified on CNV 4.14.0

Comment 3 errata-xmlrpc 2023-11-08 14:06: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 (Important: OpenShift Virtualization 4.14.0 Images security and bug fix 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:6817


Note You need to log in before you can comment on or make changes to this bug.