Loading...

XML

Word

Printable

Type: Bug
Resolution: Done
Priority: Minor
Fix Version/s: None
Affects Version/s: 4.14
Component/s: HyperShift
Labels:
- triaged

Activity Type:
Quality / Stability / Reliability
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Story Points:
None
Severity:
Low
Regression:
No

Target Backport Versions:
None
Target Version:
None
Release Blocker:
None
Sprint:
None

SFDC Cases Counter:
SFDC Cases Open:
SFDC Cases Links:

PX Impact Score:

Release Note Status:
None
Release Note Type:
None
Release Note Text:
None

Escape Reason:
None
Escape Impact:
None
Corrective Measures:
None
SDLC stage when should've been found:
None

Description of problem:

When deleting a cluster that contains persistent volumes, the CLI does not wait long enough to destroy the cluster and times out before the cluster is deleted.

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

4.13.z

How reproducible:

Often

Steps to Reproduce:

1. Create a hostedcluster on aws
2. Add persistent volumes to hosted cluster via pvcs
3. run `hypershift destroy cluster aws` to destroy the cluster

Actual results:

the destroy times out

Expected results:

the destroy succeeds

Additional info:

The workaround is to run the destroy again and it eventually succeeds.

Assignee:: Unassigned

Reporter:: Cesar Wong (Inactive)

Need Info From:: None

Contributors:: None

QA Contact:: Jie Zhao

Doc Contact:: None

Votes:: 0 Vote for this issue

Watchers:: 3 Start watching this issue

Created:: 2023/03/10 3:43 PM

Updated:: 2025/10/14 6:04 PM

Resolved:: 2025/10/14 6:04 PM