Bug 1809049
Summary: | Delete is triggered when MHC has "healthchecking.openshift.io/strategy: reboot" annotation [Azure Set up] | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | Milind Yadav <miyadav> |
Component: | Cloud Compute | Assignee: | Alberto <agarcial> |
Cloud Compute sub component: | Other Providers | QA Contact: | sunzhaohua <zhsun> |
Status: | CLOSED ERRATA | Docs Contact: | |
Severity: | unspecified | ||
Priority: | unspecified | ||
Version: | 4.4 | ||
Target Milestone: | --- | ||
Target Release: | 4.5.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | No Doc Update | |
Doc Text: | Story Points: | --- | |
Clone Of: | Environment: | ||
Last Closed: | 2020-08-04 18:03:04 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
Milind Yadav
2020-03-02 10:23:59 UTC
Annotation was renamed to `host.metal3.io/external-remediation` https://github.com/openshift/machine-api-operator/pull/476/files#diff-614d58186947ca2e4e215d42c496d72eR31 Description of problem:Delete is triggered when MHC has "healthchecking.openshift.io/strategy: reboot" annotation [Azure Set up] Version-Release number of selected component (if applicable): NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.5.0-0.nightly-2020-03-12-041748 True False 153m Cluster version is 4.5.0-0.nightly-2020-03-12-041748 Steps to Reproduce : 1.Create a mhc --- apiVersion: machine.openshift.io/v1beta1 kind: MachineHealthCheck metadata: creationTimestamp: "2020-02-14T09:47:08Z" generation: 1 name: "<User defined Name>" namespace: openshift-machine-api resourceVersion: "71059" selfLink: /apis/machine.openshift.io/v1beta1/namespaces/openshift-machine-api/machinehealthchecks/mhc-miyadav-1402-drlvf-worker-us-east-2c uid: ef74b735-e58e-4c24-aa69-015d90998b77 spec: maxUnhealthy: 3 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: - status: "False" timeout: 300s type: Ready - status: Unknown timeout: 300s type: Ready Result:MHC created successfully 2.Annotate 'reboot' remediation strategy to the mhc oc annotate mhc NAME machine.openshift.io/remediation-strategy=external-baremetal Result : annotation done successfully 3.Go to cloud provider console, stop the instance of the node Result : instance stopped successfully 4.oc get machine <machine-name> -o jsonpath="{.metadata.annotations}" Actual results:map[host.metal3.io/external-remediation: machine.openshift.io/instance-state:Running Expected results:Remediation should trigger, but should not delete the machine. Instead, should add an annotation "host.metal3.io/external-remediation" to the machine 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 image release advisory), 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:2409 |