Loading...

XML

Word

Printable

Type: Bug
Resolution: Unresolved
Priority: Undefined
Fix Version/s: None
Affects Version/s: 4.17.z
Component/s: Installer / Assisted installer
Labels:
None

Activity Type:
None
Blocked:
False
Blocked Reason:

Hide

None

Show
None
Story Points:
None
Severity:
None
Regression:
None
Architecture:

x86_64

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 destroying a cluster in ACM (v2.13) bare metal hosts (PowerEdge 6525) get stuck in 'deprovisioning'. No errors seen in metal3-ironic container.

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

    v2.13 ACM
    v4.17.40 OCP (on ACM)
    v4.18.z OCP (on deployed BM cluster)

How reproducible:

    occurs each time a cluster is destroyed

Steps to Reproduce:

    1. Deploy bare metal cluster with ACM
    2. Attempt to delete cluster manually (after GitOps

Actual results:

3 nodes remaining in deprovisioning

Expected results:

    3 nodes get deprovisioned and agents deleted

Additional info:

namespace is not being deleted
using gitops w/ prune to delete objects (failing to action prune in ArgoCD)

Assignee:: liat gamliel

Reporter:: Peter Legg

Need Info From:: None

Contributors:: None

QA Contact:: Jad Haj Yahya

Doc Contact:: None

Votes:: 0 Vote for this issue

Watchers:: 6 Start watching this issue

Created:: 2025/10/15 2:20 PM

Updated:: 2025/10/17 7:41 PM

Details

Description

Attachments

Easy Agile Planning Poker

Activity

People

Dates