Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Bug 1869318: Remove finalizer from Node on delete #97

Merged
merged 1 commit into from Aug 21, 2020

Conversation

zaneb
Copy link
Member

@zaneb zaneb commented Aug 20, 2020

Since 4dba29b we add a finalizer on the
Node corresponding to a Machine, but we only remove it when the Node is
being deleted while the Machine is still active. Remove it when the
Machine is being deleted, otherwise the Node can never be removed.

Since 4dba29b we add a finalizer on the
Node corresponding to a Machine, but we only remove it when the Node is
being deleted while the Machine is still active. Remove it when the
Machine is being deleted, otherwise the Node can never be removed.
@openshift-ci-robot openshift-ci-robot added the bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. label Aug 20, 2020
@openshift-ci-robot
Copy link

@zaneb: This pull request references Bugzilla bug 1869318, which is valid. The bug has been moved to the POST state. The bug has been updated to refer to the pull request using the external bug tracker.

3 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.6.0) matches configured target release for branch (4.6.0)
  • bug is in the state ASSIGNED, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

Bug 1869318: Remove finalizer from Node on delete

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.

@openshift-ci-robot openshift-ci-robot added the bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. label Aug 20, 2020
@zaneb
Copy link
Member Author

zaneb commented Aug 20, 2020

/assign @dhellmann
/cc @hardys
/cc @mhrivnak

Copy link

@dhellmann dhellmann left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm

@dhellmann
Copy link

/approve

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Aug 20, 2020
@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: dhellmann, zaneb

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

The pull request process is described here

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-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Aug 20, 2020
@openshift-bot
Copy link

/retest

Please review the full test history for this PR and help us cut down flakes.

@openshift-merge-robot openshift-merge-robot merged commit 7f69c2e into openshift:master Aug 21, 2020
@openshift-ci-robot
Copy link

@zaneb: All pull requests linked via external trackers have merged: openshift/cluster-api-provider-baremetal#97. Bugzilla bug 1869318 has been moved to the MODIFIED state.

In response to this:

Bug 1869318: Remove finalizer from Node on delete

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.

@stbenjam
Copy link
Member

/cherry-pick release-4.5

@openshift-cherrypick-robot

@stbenjam: #97 failed to apply on top of branch "release-4.5":

Applying: Remove finalizer from Node on delete
Using index info to reconstruct a base tree...
M	pkg/cloud/baremetal/actuators/machine/actuator.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/cloud/baremetal/actuators/machine/actuator.go
CONFLICT (content): Merge conflict in pkg/cloud/baremetal/actuators/machine/actuator.go
error: Failed to merge in the changes.
hint: Use 'git am --show-current-patch=diff' to see the failed patch
Patch failed at 0001 Remove finalizer from Node on delete
When you have resolved this problem, run "git am --continue".
If you prefer to skip this patch, run "git am --skip" instead.
To restore the original branch and stop patching, run "git am --abort".

In response to this:

/cherry-pick release-4.5

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.

@zaneb
Copy link
Member Author

zaneb commented Aug 24, 2020

The bug is not present in release-4.5.

honza pushed a commit to honza/cluster-api-provider-baremetal that referenced this pull request Feb 7, 2022
🐛 Fix bug when cluster is not found
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. lgtm Indicates that a PR is ready to be merged.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

7 participants