-
Notifications
You must be signed in to change notification settings - Fork 462
Bug 1829923: etcd-quorum-guard: update containers section in deployment.yaml #1818
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 1829923: etcd-quorum-guard: update containers section in deployment.yaml #1818
Conversation
|
/retitle Bug 1829923: etcd-quorum-guard: move failure threshold/timeout to under readiness |
|
@kikisdeliveryservice: This pull request references Bugzilla bug 1829923, which is invalid:
Comment DetailsIn response to this:
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. |
1 similar comment
|
@kikisdeliveryservice: This pull request references Bugzilla bug 1829923, which is invalid:
Comment DetailsIn response to this:
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. |
|
/bugzilla refresh |
|
@ironcladlou: This pull request references Bugzilla bug 1829923, which is valid. The bug has been updated to refer to the pull request using the external bug tracker. 3 validation(s) were run on this bug
DetailsIn response to this:
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. |
|
cc: @wking |
de94602 to
4d11568
Compare
|
@kikisdeliveryservice: This pull request references Bugzilla bug 1829923, which is valid. 3 validation(s) were run on this bug
DetailsIn response to this:
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. |
|
/test e2e-aws |
|
e2e-aws seems to have some issues..
/test e2e-aws |
|
LGTM in principle, let's confirm we see expected results. |
cool after this is confirmed we can cherrypick to 4.5 |
Hmmm... |
|
i think the containers section is off maybe? |
|
other platforms are doing it in this format:
|
Made the following changes as settings were not getting picked up: - move failure threshold/timeout to nest under readinessProbe - move and correct initialDelaySeconds and periodSeconds - reorder container sub-elements to nest image under name
|
/lgtm Pull the hold when the results look good :) |
2763493 to
9d62f94
Compare
|
@kikisdeliveryservice: This pull request references Bugzilla bug 1829923, which is valid. 3 validation(s) were run on this bug
DetailsIn response to this:
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. |
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: kikisdeliveryservice, wking The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
@kikisdeliveryservice: The following tests failed, say
Full PR test history. Your PR dashboard. Please help us cut down on flakes by linking to an open issue when you hit one in your PR. DetailsInstructions 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. |
|
reconfirming in this e2e-aws run: e2e-aws deployments.json check: And also: $ curl -s https://storage.googleapis.com/origin-ci-test/pr-logs/pull/openshift_machine-config-operator/1818/pull-ci-openshift-machine-config-operator-master-e2e-aws/1271220314893717504/artifacts/e2e-aws/gather-extra/pods.json | jq -r '.items[] | select(.metadata.name | contains("quorum-guard")).spec.containers[] | select(.name == "guard").readinessProbe | {initialDelaySeconds, periodSeconds, failureThreshold, timeoutSeconds} | tostring' e2e-gcp-op pods.json check: |
|
rhel7 and metal-ipi seem to have RBAC issues /skip |
|
Since I've confirmed this 2x am lifting hold to merge /hold cancel |
|
@kikisdeliveryservice: All pull requests linked via external trackers have merged: openshift/machine-config-operator#1818, openshift/machine-config-operator#1797. Bugzilla bug 1829923 has been moved to the MODIFIED state. DetailsIn response to this:
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. |
|
/cherry-pick release-4.5 |
|
@kikisdeliveryservice: #1818 failed to apply on top of branch "release-4.5": DetailsIn response to this:
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. |
|
Backports for 4.4 & 4.5: Also fixed the BZs to link correctly to the open PRs 😄 @ironcladlou @hexfusion PTAL at the above backports |
|
I don't see the right values in https://storage.googleapis.com/origin-ci-test/pr-logs/pull/openshift_machine-config-operator/1818/pull-ci-openshift-machine-config-operator-master-e2e-gcp-upgrade/1271220339220680704/artifacts/e2e-gcp-upgrade/pods.json Which is somewhat concerning. I don't know how to explain the discrepancy yet. I'm running an upgrade test against #1819 to exercise 4.4 -> 4.5 and see what happens. |
Interesting... that could explain the upgrade results. Still waiting on my Y upgrade run to confirm the issue. |
|
Wanted to test a Y upgrade but cluster-bot didn't like that this PR was merged so I went with #1819: |
Made the following changes as settings were not getting
picked up: