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

[release-4.5] Bug 1874597: static-pod-installer: remove deadlock by recreating installers that disappear #278

Merged
merged 1 commit into from Sep 17, 2020

Conversation

soltysh
Copy link
Member

@soltysh soltysh commented Sep 4, 2020

…allers that disappear

/assign @sttts

@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 Sep 4, 2020
@openshift-ci-robot
Copy link

@soltysh: This pull request references Bugzilla bug 1874597, which is invalid:

  • expected the bug to target the "4.6.0" release, but it targets "4.5.z" 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 1874597: static-pod-installer: remove deadlock by recreating inst…

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/invalid-bug Indicates that a referenced Bugzilla bug is invalid for the branch this PR is targeting. needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. labels Sep 4, 2020
@openshift-ci-robot openshift-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Sep 4, 2020
@soltysh soltysh changed the title Bug 1874597: static-pod-installer: remove deadlock by recreating inst… [release-4.5] Bug 1874597: static-pod-installer: remove deadlock by recreating inst… Sep 4, 2020
@soltysh soltysh changed the base branch from master to release-4.5 September 4, 2020 08:28
@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 Sep 4, 2020
@openshift-ci-robot
Copy link

@soltysh: This pull request references Bugzilla bug 1874597, which is valid. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.5.z) matches configured target release for branch (4.5.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 1858763 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA))
  • dependent Bugzilla bug 1858763 targets the "4.6.0" release, which is one of the valid target releases: 4.6.0, 4.6.z
  • bug has dependents

In response to this:

[release-4.5] Bug 1874597: static-pod-installer: remove deadlock by recreating inst…

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.

@soltysh soltysh closed this Sep 4, 2020
@soltysh soltysh reopened this Sep 4, 2020
@openshift-ci-robot
Copy link

@soltysh: This pull request references Bugzilla bug 1874597. The bug has been updated to no longer refer to the pull request using the external bug tracker.

In response to this:

[release-4.5] Bug 1874597: static-pod-installer: remove deadlock by recreating inst…

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 removed the needs-rebase Indicates a PR cannot be merged because it has merge conflicts with HEAD. label Sep 4, 2020
@openshift-ci-robot
Copy link

@soltysh: This pull request references Bugzilla bug 1874597, which is valid. The bug has been updated to refer to the pull request using the external bug tracker.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.5.z) matches configured target release for branch (4.5.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 1858763 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA))
  • dependent Bugzilla bug 1858763 targets the "4.6.0" release, which is one of the valid target releases: 4.6.0, 4.6.z
  • bug has dependents

In response to this:

[release-4.5] Bug 1874597: static-pod-installer: remove deadlock by recreating inst…

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.

@soltysh
Copy link
Member Author

soltysh commented Sep 7, 2020

/retest

2 similar comments
@ingvagabund
Copy link
Member

/retest

@soltysh
Copy link
Member Author

soltysh commented Sep 9, 2020

/retest

@damemi
Copy link

damemi commented Sep 9, 2020

This prometheus flake is annoying, and I have no idea what causes it. We tried extending the timeout in #271 but that clearly isn't enough:

 --- FAIL: TestMetricsAccessible (30.84s)
    scheduler_test.go:317: prometheus returned unexpected results: timed out waiting for the condition
FAIL
FAIL	github.com/openshift/cluster-kube-scheduler-operator/test/e2e	43.570s
FAIL

@sttts
Copy link
Contributor

sttts commented Sep 11, 2020

/retest
/lgtm

@openshift-bot
Copy link
Contributor

/retest

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

@xingxingxia
Copy link

/bugzilla cc-qa

@openshift-ci-robot
Copy link

@xingxingxia: This pull request references Bugzilla bug 1874597, which is valid.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.5.z) matches configured target release for branch (4.5.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 1858763 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA))
  • dependent Bugzilla bug 1858763 targets the "4.6.0" release, which is one of the valid target releases: 4.6.0, 4.6.z
  • bug has dependents

No GitHub users were found matching the public email listed for the QA contact in Bugzilla (kewang@redhat.com), skipping review request.

In response to this:

/bugzilla cc-qa

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.

@wangke19
Copy link

/bugzilla cc-qa

@openshift-ci-robot
Copy link

@wangke19: This pull request references Bugzilla bug 1874597, which is valid.

6 validation(s) were run on this bug
  • bug is open, matching expected state (open)
  • bug target release (4.5.z) matches configured target release for branch (4.5.z)
  • bug is in the state POST, which is one of the valid states (NEW, ASSIGNED, ON_DEV, POST, POST)
  • dependent bug Bugzilla bug 1858763 is in the state VERIFIED, which is one of the valid states (VERIFIED, RELEASE_PENDING, CLOSED (ERRATA))
  • dependent Bugzilla bug 1858763 targets the "4.6.0" release, which is one of the valid target releases: 4.6.0, 4.6.z
  • bug has dependents

Requesting review from QA contact:
/cc @wangke19

In response to this:

/bugzilla cc-qa

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.

@wangke19
Copy link

/lgtm

@openshift-ci-robot
Copy link

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: soltysh, sttts, wangke19

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

@wangke19
Copy link

Launched one 4.5 cluster with this PR successfully, it worked fine.

@markmc markmc changed the title [release-4.5] Bug 1874597: static-pod-installer: remove deadlock by recreating inst… [release-4.5] Bug 1874597: static-pod-installer: remove deadlock by recreating installers that disappear Sep 17, 2020
@markmc
Copy link

markmc commented Sep 17, 2020

Risk assessment made difficult here because the critical 9 line fix we need ends up as a +749 −298 diff because of the necessary revendoring. Approving nonetheless, especially since we've merged this for ceo and ckao already.

@markmc markmc added the cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. label Sep 17, 2020
@openshift-merge-robot openshift-merge-robot merged commit eaaf196 into openshift:release-4.5 Sep 17, 2020
@openshift-ci-robot
Copy link

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

Bugzilla bug 1874597 has been moved to the MODIFIED state.

In response to this:

[release-4.5] Bug 1874597: 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.

@soltysh soltysh deleted the bug1874597 branch September 23, 2020 11:42
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. cherry-pick-approved Indicates a cherry-pick PR into a release branch has been approved by the release branch manager. 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

10 participants