Bug 1851531
Summary: | BMO can get into hot reconcile loop when changing Status | |||
---|---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Zane Bitter <zbitter> | |
Component: | Bare Metal Hardware Provisioning | Assignee: | Zane Bitter <zbitter> | |
Bare Metal Hardware Provisioning sub component: | baremetal-operator | QA Contact: | Raviv Bar-Tal <rbartal> | |
Status: | CLOSED ERRATA | Docs Contact: | ||
Severity: | high | |||
Priority: | unspecified | CC: | augol, beth.white, shardy | |
Version: | 4.5 | Keywords: | Triaged | |
Target Milestone: | --- | |||
Target Release: | 4.5.z | |||
Hardware: | Unspecified | |||
OS: | Unspecified | |||
Whiteboard: | ||||
Fixed In Version: | Doc Type: | Bug Fix | ||
Doc Text: |
Cause: The controller for BareMetalHost objects mirrored status data, including a timestamp of the latest status update, to an annotation (which was not needed by OpenShift). This could result in the BareMetalHost entering a state of continuous flux.
Consequence: Affected BareMetalHosts would be subject to longer and longer back-offs between reconciliation to prevent the controller overwhelming the Kubernetes API.
Fix: The annotation causing the problem is no longer written.
Result: BareMetalHost objects are reconciled as scheduled.
|
Story Points: | --- | |
Clone Of: | 1851530 | |||
: | 1851532 (view as bug list) | Environment: | ||
Last Closed: | 2020-09-08 10:54:03 UTC | Type: | --- | |
Regression: | --- | Mount Type: | --- | |
Documentation: | --- | CRM: | ||
Verified Versions: | Category: | --- | ||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | ||
Cloudforms Team: | --- | Target Upstream Version: | ||
Embargoed: | ||||
Bug Depends On: | 1851530 | |||
Bug Blocks: | 1851532 |
Description
Zane Bitter
2020-06-26 20:35:56 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.5.8 bug fix update), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2020:3510 |