Bug 2237877 - Populators with retainAfterCompletion annotation
Summary: Populators with retainAfterCompletion annotation
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.1
Assignee: Álvaro Romero
QA Contact: Jenia Peimer
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-09-07 12:51 UTC by Jenia Peimer
Modified: 2023-12-07 15:00 UTC (History)
3 users (show)

Fixed In Version: CNV- v4.14.1.rhel9-17
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-12-07 15:00:46 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Github kubevirt containerized-data-importer pull 2910 0 None Merged [release-v1.57] Manual backport of AnnPodRetainAfterCompletion with populators 2023-11-15 19:15:48 UTC
Red Hat Issue Tracker CNV-32770 0 None None None 2023-09-07 12:54:34 UTC
Red Hat Product Errata RHSA-2023:7704 0 None None None 2023-12-07 15:00:48 UTC

Description Jenia Peimer 2023-09-07 12:51:45 UTC
Description of problem:
Adding the DV annotation
  'cdi.kubevirt.io/storage.pod.retainAfterCompletion: "true"'
should cause CDI transfer pods (importer, uploader, cloner) to be retained after a successful or failed completion. 

Alexander noticed that adding this annotation triggers a non-Populators flow. 

It means that some of the tier1 tests are not running with Populators flow.

We should consider it as a blocker for 4.14.


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

How reproducible:
Always

Steps to Reproduce:
1. Add annotation to the DV:
    'cdi.kubevirt.io/storage.pod.retainAfterCompletion: "true"'
2. See DV/PVC annotation - Populators were not used


Actual results:
non-populators flow

Expected results:
populators flow

Comment 2 Jenia Peimer 2023-11-16 09:42:50 UTC
Verified on CNV v4.14.1.rhel9-17

$ oc get dv
NAME            PHASE       PROGRESS   RESTARTS   AGE
dv-source-hpp   Succeeded   100.0%     1          68s

$ oc get pvc
NAME                                                 STATUS   VOLUME                                     CAPACITY   ACCESS MODES   STORAGECLASS         AGE
dv-source-hpp                                        Bound    pvc-2da05ee7-a964-4bfd-9d26-2aaa35190e61   149Gi      RWO            hostpath-csi-basic   70s
prime-f5e8a560-d925-484e-8302-55cd2a89fbdb           Lost     pvc-2da05ee7-a964-4bfd-9d26-2aaa35190e61   0                         hostpath-csi-basic   69s
prime-f5e8a560-d925-484e-8302-55cd2a89fbdb-scratch   Bound    pvc-514d4526-b161-4e02-8643-2c54bc5a49de   149Gi      RWO            hostpath-csi-basic   53s

$ oc get pods
NAME                                                  READY   STATUS      RESTARTS   AGE
importer-prime-f5e8a560-d925-484e-8302-55cd2a89fbdb   0/1     Completed   0          66s

Comment 9 errata-xmlrpc 2023-12-07 15:00:46 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.1 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:7704


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