Bug 1875558 - BareMetalHost resources are not always deleted
Summary: BareMetalHost resources are not always deleted
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Bare Metal Hardware Provisioning
Version: 4.6
Hardware: Unspecified
OS: Unspecified
Target Milestone: ---
: 4.6.0
Assignee: Doug Hellmann
QA Contact: Daniel
Depends On:
Blocks: 1874599
TreeView+ depends on / blocked
Reported: 2020-09-03 18:41 UTC by Doug Hellmann
Modified: 2020-10-27 16:38 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Last Closed: 2020-10-27 16:37:51 UTC
Target Upstream Version:

Attachments (Terms of Use)

System ID Private Priority Status Summary Last Updated
Github metal3-io baremetal-operator issues 482 0 None closed baremetalhost is not removed 2020-10-27 14:09:16 UTC
Github openshift baremetal-operator pull 96 0 None closed Bug 1875558: Always delete found host from Ironic on deletion 2020-10-27 14:09:17 UTC
Red Hat Product Errata RHBA-2020:4196 0 None None None 2020-10-27 16:38:04 UTC

Description Doug Hellmann 2020-09-03 18:41:37 UTC
Description of problem:

Upstream bug https://github.com/metal3-io/baremetal-operator/issues/482 says that if hosts are registered and then deleted quickly in succession the host is not actually removed.

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


How reproducible:

Reliably, but it's tricky to get the timing right.

Steps to Reproduce:
1. Create the host and then delete it immediately

Actual results:

Errors in the log and the host is not deleted.

Expected results:

The host is cleanly deleted.

Additional info:

Comment 5 errata-xmlrpc 2020-10-27 16:37:51 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 (OpenShift Container Platform 4.6 GA Images), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


Note You need to log in before you can comment on or make changes to this bug.