Bug 1872147
| Summary: | Disable health checks if BMO is not running or BMH is in unmanaged state | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Rastislav Wagner <rawagner> |
| Component: | Console Metal3 Plugin | Assignee: | Rastislav Wagner <rawagner> |
| Status: | CLOSED ERRATA | QA Contact: | Yanping Zhang <yanpzhan> |
| Severity: | medium | Docs Contact: | |
| Priority: | high | ||
| Version: | 4.6 | CC: | aos-bugs, jtomasek, yapei |
| Target Milestone: | --- | ||
| Target Release: | 4.6.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | If docs needed, set a value | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2020-10-27 16:32:58 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Rastislav Wagner
2020-08-25 07:56:16 UTC
Little bit more info: BMO is not running if there's no provisioning-configuration CR (BMO pods are running, but BMO is disabled due to missing CR). 1. Create MachineHealthCheck matching two worker nodes
$ cat mhc.yaml
apiVersion: machine.openshift.io/v1beta1
kind: MachineHealthCheck
metadata:
name: example
namespace: openshift-machine-api
spec:
selector:
matchLabels:
machine.openshift.io/cluster-api-cluster: <your cluster name>
machine.openshift.io/cluster-api-machine-role: worker
machine.openshift.io/cluster-api-machine-type: worker
machine.openshift.io/cluster-api-machineset: <your machine set>
unhealthyConditions:
- type: Ready
status: Unknown
timeout: 300s
- type: Ready
status: 'False'
timeout: 300s
maxUnhealthy: 40%
$ oc create -f mhc.yaml
2. Check `Health Checks` status on Nodes -> Click on name of worker-0-1/worker-0-0 -> Check 'Health Checks' status in 'Status' card, it shows "2 conditions passing
" and green ok icon
3. Delete provisioning-configuration
$ oc delete provisioning.metal3.io provisioning-configuration
provisioning.metal3.io "provisioning-configuration" deleted
4. Check `Health Checks` status again using same steps with step2, this time it will show 'Not available' and grey question mark ?
Moving to VERIFIED 4.6.0-0.nightly-2020-09-27-075304
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. https://access.redhat.com/errata/RHBA-2020:4196 |