-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
4.14
-
None
-
None
-
Metal Platform 260, Metal Platform 261, Metal Platform 263
-
3
-
False
-
Description of problem:
For clusters built using the Assisted Installer, it's not possible to delete the BMH. The hosts go into a deprovisioning state and get stuck. It is always necessary to remove the finalizer to complete the deprovisioning process. Another issue arises during host reprovisioning, where a MAC address conflict occurs with an existing node that has already been removed.
Version-Release number of selected component (if applicable):
How reproducible:
always
Steps to Reproduce:
1. Execute deprovisioning hosts 2. Remove finalizer since it stuck 3. Unable to reprovision due to a MAC address conflict
Actual results:
Unable to de-provision and re-provision
Expected results:
The customer expects the deprovisioning step to be a one-time task (without requiring the removal of the finalizer) and also expects any cached data to be cleaned, allowing for a smooth reprovisioning process.
Additional info:
MG included in the comment
- is related to
-
OCPBUGS-44026 BaremetalHosts stuck in 'provisioning' state despite deploy_step success
- New