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 1858763: static-pod-installer: remove deadlock by recreating installers that disappear #871

Conversation

sttts
Copy link
Contributor

@sttts sttts commented Aug 26, 2020

The line

ret.TargetRevision = currNodeState.CurrentRevision

led to a dead-lock because the installer controller only does anything if either

  • all TargetRevisions are zero
  • or the TargetRevision value is larger than CurrentRevision.

We went into the second case and the controller dead-locked.

Note: just before this code there is the ensureInstallerPod invocation. We run into the bug when the pod apply call fails (e.g. of some network issue).

Note: when the installer pod disappears again and again (for whatever reason), this could hotloop (of course we do the usual backoff in the controller though). But this is the same
for the existing OOM case.

The line

```
ret.TargetRevision = currNodeState.CurrentRevision
```

led to a dead-lock because the installer controller only does anything if either

- all `TargetRevision`s are zero
- or the `TargetRevision` value is larger than `CurrentRevision`.

We went into the second case and the controller dead-locked.
@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 26, 2020
@sttts sttts changed the title static-pod-installer: recreate installers that disappeared Bug 1858763: static-pod-installer: remove deadlock by recreating installers that disappear Aug 26, 2020
@openshift-ci-robot
Copy link

@sttts: This pull request references Bugzilla bug 1858763, which is invalid:

  • expected the bug to target the "4.6.0" release, but it targets "---" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Bug 1858763: static-pod-installer: remove deadlock by recreating installers that disappear

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 bugzilla/severity-high Referenced Bugzilla bug's severity is high for the branch this PR is targeting. bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Aug 26, 2020
@openshift-ci-robot
Copy link

@sttts: This pull request references Bugzilla bug 1858763, which is invalid:

  • expected the bug to target the "4.6.0" release, but it targets "---" instead

Comment /bugzilla refresh to re-evaluate validity if changes to the Bugzilla bug are made, or edit the title of this pull request to link to a different bug.

In response to this:

Bug 1858763: static-pod-installer: remove deadlock by recreating installers that disappear

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.

@sttts
Copy link
Contributor Author

sttts commented Aug 26, 2020

/bugzilla refresh

@openshift-ci-robot openshift-ci-robot added bugzilla/valid-bug Indicates that a referenced Bugzilla bug is valid for the branch this PR is targeting. and removed bugzilla/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. labels Aug 26, 2020
@openshift-ci-robot
Copy link

@sttts: This pull request references Bugzilla bug 1858763, 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 NEW, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)

In response to this:

/bugzilla refresh

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.

@mfojtik
Copy link
Member

mfojtik commented Aug 26, 2020

/lgtm

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

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mfojtik, sttts

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

@sttts
Copy link
Contributor Author

sttts commented Aug 26, 2020

/hold

until proof bump openshift/cluster-kube-apiserver-operator#939 shows some green.

@openshift-ci-robot openshift-ci-robot added the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Aug 26, 2020
@openshift-merge-robot openshift-merge-robot merged commit 025aa3f into openshift:master Aug 26, 2020
@openshift-ci-robot
Copy link

@sttts: All pull requests linked via external trackers have merged:

Bugzilla bug 1858763 has been moved to the MODIFIED state.

In response to this:

Bug 1858763: static-pod-installer: remove deadlock by recreating installers that disappear

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.

@sttts
Copy link
Contributor Author

sttts commented Sep 4, 2020

/cherry-pick release-4.5

@sttts
Copy link
Contributor Author

sttts commented Sep 4, 2020

/cherry-pick release-4.4

@openshift-cherrypick-robot

@sttts: new pull request created: #879

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.

@openshift-cherrypick-robot

@sttts: #871 failed to apply on top of branch "release-4.4":

Applying: static-pod-installer: recreate installers that disappeared
Using index info to reconstruct a base tree...
M	pkg/operator/staticpod/controller/installer/installer_controller.go
Falling back to patching base and 3-way merge...
Auto-merging pkg/operator/staticpod/controller/installer/installer_controller.go
CONFLICT (content): Merge conflict in pkg/operator/staticpod/controller/installer/installer_controller.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 static-pod-installer: recreate installers that disappeared
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.4

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.

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. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. 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

5 participants