Skip to content

[release-4.7] Changing the default behaviour of the CAPBM to request hard reboot#143

Closed
openshift-cherrypick-robot wants to merge 2 commits intoopenshift:release-4.7from
openshift-cherrypick-robot:cherry-pick-138-to-release-4.7
Closed

[release-4.7] Changing the default behaviour of the CAPBM to request hard reboot#143
openshift-cherrypick-robot wants to merge 2 commits intoopenshift:release-4.7from
openshift-cherrypick-robot:cherry-pick-138-to-release-4.7

Conversation

@openshift-cherrypick-robot

This is an automated cherry-pick of #138

/assign rdoxenham

In this commit we're pulling in the latest version of the BMO
dependencies via the vendor module, allowing us to utilise newer
functions and structs provided by recent PR's in the latest BMO
code. This updates to v0.0.0-20210303141721-86a42dcb0150.
This change adds an additional mode to the reboot annotation that
forces all nodes sent for remediation, e.g. via a MachineHealthCheck,
to be forcefully rebooted rather than defaulting to a soft reboot
first, as it is today. The primary drive behind this change is to
enable quicker recovery of workloads, e.g. for high-availability
use cases, and by defaulting to forced hard reboot we can enable
functionality very close to fencing. This change shouldn't impact
any other non-remediation reboot requests, as the hard reboot
functionality only takes place when the mode=hard annotation is
applied to the node.

All of the work on the BMO can be found in the link below. Whilst
we depend on this PR to have a complete solution, we don't have a
hard dependency on them merging together.

BMO PR: metal3-io/baremetal-operator#795
@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: openshift-cherrypick-robot
To complete the pull request process, please assign dhellmann after the PR has been reviewed.
You can assign the PR to them by writing /assign @dhellmann in a comment when ready.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-ci
Copy link

openshift-ci bot commented Mar 9, 2021

@openshift-cherrypick-robot: The following tests failed, say /retest to rerun all failed tests:

Test name Commit Details Rerun command
ci/prow/generate-check 079ca16 link /test generate-check
ci/prow/e2e-metal-ipi-virtualmedia 079ca16 link /test e2e-metal-ipi-virtualmedia

Full PR test history. Your PR dashboard.

Details

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. I understand the commands that are listed here.

@rdoxenham
Copy link

I will need to create a separate PR for this as I need to pull in #140 manually.

@hardys
Copy link

hardys commented Mar 9, 2021

/close

@openshift-ci-robot
Copy link

@hardys: Closed this PR.

Details

In response to this:

/close

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

honza pushed a commit to honza/cluster-api-provider-baremetal that referenced this pull request Feb 7, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants