Bug 2240966

Summary: DataVolume initial status is None
Product: Container Native Virtualization (CNV) Reporter: vsibirsk
Component: StorageAssignee: Adam Litke <alitke>
Status: CLOSED MIGRATED QA Contact: Kevin Alon Goldblatt <kgoldbla>
Severity: low Docs Contact:
Priority: low    
Version: 4.14.0CC: dafrank, jpeimer, mhenriks, ycui
Target Milestone: ---   
Target Release: 4.15.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2023-12-14 16:04:29 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:
Embargoed:

Description vsibirsk 2023-09-27 11:42:10 UTC
Description of problem:
After creating DataVolume, it's status is None

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

How reproducible:
100%

Steps to Reproduce:
1.Create DataVolume and monitor it's status (oc get dv -w)
2.
3.

Actual results:
DV has None status before changing so some other valid status

Expected results:
DV has valid status right after creation

Additional info:
Affects QE automation since it expects a valid DV status
Status change of DV created in golden-image NS, then cloned to VM NS
openshift-virtualization-os-images   fedora-38                                                       0s
openshift-virtualization-os-images   fedora-38                                                       0s
openshift-virtualization-os-images   fedora-38                     ImportScheduled   N/A                   0s
openshift-virtualization-os-images   fedora-38                     ImportScheduled   N/A                   2s
openshift-virtualization-os-images   fedora-38                     ImportInProgress   N/A                   14s
openshift-virtualization-os-images   fedora-38                     ImportInProgress   N/A                   16s
openshift-virtualization-os-images   fedora-38                     ImportInProgress   N/A        1          17s
openshift-virtualization-os-images   fedora-38                     ImportInProgress   N/A        1          18s
openshift-virtualization-os-images   fedora-38                     ImportScheduled    N/A        1          19s
openshift-virtualization-os-images   fedora-38                     ImportScheduled    N/A        1          22s
openshift-virtualization-os-images   fedora-38                     ImportInProgress   N/A        1          24s
openshift-virtualization-os-images   fedora-38                     ImportInProgress   7.14%      1          30s
openshift-virtualization-os-images   fedora-38                     ImportInProgress   8.14%      1          31s
openshift-virtualization-os-images   fedora-38                     ImportInProgress   14.15%     1          33s
openshift-virtualization-os-images   fedora-38                     ImportInProgress   14.15%     1          33s
openshift-virtualization-os-images   fedora-38                     ImportInProgress   21.17%     1          35s
openshift-virtualization-os-images   fedora-38                     ImportInProgress   29.19%     1          37s
openshift-virtualization-os-images   fedora-38                     ImportInProgress   36.21%     1          39s
openshift-virtualization-os-images   fedora-38                     ImportInProgress   44.22%     1          41s
openshift-virtualization-os-images   fedora-38                     ImportInProgress   51.24%     1          43s
openshift-virtualization-os-images   fedora-38                     ImportInProgress   52.24%     1          43s
openshift-virtualization-os-images   fedora-38                     ImportInProgress   58.26%     1          45s
openshift-virtualization-os-images   fedora-38                     ImportInProgress   64.27%     1          47s
openshift-virtualization-os-images   fedora-38                     ImportInProgress   68.29%     1          49s
openshift-virtualization-os-images   fedora-38                     ImportInProgress   69.29%     1          49s
openshift-virtualization-os-images   fedora-38                     ImportInProgress   75.30%     1          51s
openshift-virtualization-os-images   fedora-38                     ImportInProgress   81.32%     1          53s
openshift-virtualization-os-images   fedora-38                     ImportInProgress   87.33%     1          55s
openshift-virtualization-os-images   fedora-38                     ImportInProgress   94.58%     1          57s
openshift-virtualization-os-images   fedora-38                     ImportInProgress   99.59%     1          59s
openshift-virtualization-os-images   fedora-38                     ImportInProgress   99.59%     1          61s
openshift-virtualization-os-images   fedora-38                     Succeeded          100.0%     1          62s
openshift-virtualization-os-images   fedora-38                     Succeeded          100.0%     1          62s
supported-os-common-templates-fedora-test-fedora-os-support   fedora-38-1695808352-275581                                            1s
supported-os-common-templates-fedora-test-fedora-os-support   fedora-38-1695808352-275581                                            1s
supported-os-common-templates-fedora-test-fedora-os-support   fedora-38-1695808352-275581                                            1s
supported-os-common-templates-fedora-test-fedora-os-support   fedora-38-1695808352-275581                                            1s
supported-os-common-templates-fedora-test-fedora-os-support   fedora-38-1695808352-275581   CSICloneInProgress   N/A                   1s
supported-os-common-templates-fedora-test-fedora-os-support   fedora-38-1695808352-275581   CSICloneInProgress   N/A                   1s
supported-os-common-templates-fedora-test-fedora-os-support   fedora-38-1695808352-275581   CSICloneInProgress   N/A                   3s
supported-os-common-templates-fedora-test-fedora-os-support   fedora-38-1695808352-275581   CSICloneInProgress   N/A                   3s
supported-os-common-templates-fedora-test-fedora-os-support   fedora-38-1695808352-275581   CSICloneInProgress   N/A                   3s
supported-os-common-templates-fedora-test-fedora-os-support   fedora-38-1695808352-275581   Succeeded            100.0%                3s
supported-os-common-templates-fedora-test-fedora-os-support   fedora-38-1695808352-275581   Succeeded            100.0%                3s
supported-os-common-templates-fedora-test-fedora-os-support   fedora-38-1695808352-275581   Succeeded            100.0%                5m39s

Comment 1 dalia 2023-09-27 12:30:17 UTC
Michael, should DataVolume should have an initial status of pending?

Comment 2 Michael Henriksen 2023-10-24 21:23:28 UTC
Do you know if/what other fields in the status are set when the phase is empty?

Regardless, I don't think this is something you should rely on.  DataVolume status is initially blank when created by the user.

I wouldn't be too concerned about this unless the status field is empty for a long time.  Or there are other fields set in the status while the phase is blank