Bug 2233413 - Recreating hyperconverged CR is stuck in progressing state
Summary: Recreating hyperconverged CR is stuck in progressing state
Keywords:
Status: CLOSED DUPLICATE of bug 2087608
Alias: None
Product: Container Native Virtualization (CNV)
Classification: Red Hat
Component: Installation
Version: 4.14.0
Hardware: All
OS: Linux
unspecified
medium
Target Milestone: ---
: 4.14.0
Assignee: Simone Tiraboschi
QA Contact: SATHEESARAN
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2023-08-22 07:36 UTC by SATHEESARAN
Modified: 2023-08-23 10:15 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-08-23 10:14:52 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker CNV-32311 0 None None None 2023-08-22 08:05:07 UTC

Description SATHEESARAN 2023-08-22 07:36:09 UTC 
Description of problem:
-----------------------
After deleting HCO CR and recreating it, leads to CR waiting in 'progressing' state and never completes.

Version-Release number of selected component (if applicable):
-------------------------------------------------------------
CNV v4.14.0 interim build - v4.14.0.rhel9-1664

How reproducible:
-----------------
Always

Steps to Reproduce:
-------------------
1. Delete HCO CR
# oc delete hco kubevirt-hyperconverged -n openshift-cnv
2. Wait for all the terminating pods in 'openshift-cnv' namespace to terminate
3. Create HCO CR
# oc apply -f hco.yaml

Actual results:
---------------
HCO CR creating is stuck in progressing state

Expected results:
-----------------
HCO CR should be created successfully
Comment 2 SATHEESARAN 2023-08-23 10:14:52 UTC 
Just realized that this bug is the same as the existing one which I reported for 4.11.
So the same issue is still pending

*** This bug has been marked as a duplicate of bug 2087608 ***
Note You need to log in before you can comment on or make changes to this bug.