Bug 2062321

Summary: when update attempt of hco.spec with storage classes failed, csv git stuck in installing state
Product: Container Native Virtualization (CNV) Reporter: Debarati Basu-Nag <dbasunag>
Component: InstallationAssignee: Simone Tiraboschi <stirabos>
Status: CLOSED ERRATA QA Contact: SATHEESARAN <sasundar>
Severity: high Docs Contact:
Priority: unspecified    
Version: 4.9.3CC: cnv-qe-bugs, stirabos
Target Milestone: ---   
Target Release: 4.10.1   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: hco-bundle-registry:v4.10.1-36 Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-05-18 20:27:26 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:

Comment 2 SATHEESARAN 2022-04-27 13:53:16 UTC 
Verified with hco-bundle-v4.10.1-88 with index image[1] with the following steps.

1. Delete SSP CR
      # oc delete ssp ssp-kubevirt-hyperconverged -n openshift-cnv

2. Check for CSV's status.conditions
# [cnv-qe-jenkins@ ~]$ oc get csv kubevirt-hyperconverged-operator.v4.10.1 -n openshift-cnv -o json | jq '.status.conditions[-1]'
{
  "lastTransitionTime": "2022-04-27T09:39:52Z",
  "lastUpdateTime": "2022-04-27T09:39:52Z",
  "message": "install strategy completed with no errors",
  "phase": "Succeeded",
  "reason": "InstallSucceeded"
}
There is no "Pending" phase with "InstallWaiting"
With this information marking this bug as verified.

On the other hand, I have also verified the behavior with CNV-4.9.4, where the issue was recorded originally.

When repeating the above 2 steps with CNV 4.9.4, CSV's .status.conditions shows the failure.
[cnv-qe-jenkins@ ~]$ oc get csv kubevirt-hyperconverged-operator.v4.9.4 -n openshift-cnv -o json | jq '.status.conditions[-1]'
{
  "lastTransitionTime": "2022-04-27T13:40:26Z",
  "lastUpdateTime": "2022-04-27T13:40:37Z",
  "message": "installing: waiting for deployment hco-operator to become ready: deployment \"hco-operator\" not available: Deployment does not have minimum availability.",
  "phase": "Installing",
  "reason": "InstallWaiting"
}
In this case of CNV-4.9.4, restarting hco-operator solved the problem
[cnv-qe-jenkins@ ~]$ oc delete -n openshift-cnv $(oc get pod -n openshift-cnv -l name=hyperconverged-cluster-operator -o name)
pod "hco-operator-d89477897-6ngqr" deleted

[cnv-qe-jenkins@ ~]$ oc get csv kubevirt-hyperconverged-operator.v4.10.1 -n openshift-cnv -o json | jq '.status.conditions[-1]'
{
  "lastTransitionTime": "2022-04-27T13:50:17Z",
  "lastUpdateTime": "2022-04-27T13:50:17Z",
  "message": "waiting for install components to report healthy",
  "phase": "Installing",
  "reason": "InstallSucceeded"
}


[1]- registry-proxy.engineering.redhat.com/rh-osbs/iib:220170
Comment 8 errata-xmlrpc 2022-05-18 20:27:26 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.10.1 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-2022:4668