-
Notifications
You must be signed in to change notification settings - Fork 1.4k
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
data/aws/vpc/master-elb: Set thresholds back to two #1629
data/aws/vpc/master-elb: Set thresholds back to two #1629
Conversation
These were changes from two to three in 16dfbb3 (data/aws: use nlbs instead of elbs, 2019-11-01, openshift#594): $ git show 16dfbb3 | grep _threshold | sort | uniq - healthy_threshold = 2 - # healthy_threshold = 2 + healthy_threshold = 3 - unhealthy_threshold = 2 - # unhealthy_threshold = 2 + unhealthy_threshold = 3 Alex doesn't remember intentionally making that change, and the lower thresholds will hopefully help mitigate some issues with continued connection attempts to API servers which are in the process of shutting down.
/hold We want to give this a few rounds in CI and see how it goes. |
Also in flight in this space: openshift/machine-config-operator#638 |
Hrm. I guess I'll kick this again just to start assembing some more statistics... /retest |
/test e2e-metal |
I ran a number of local stress tests with 2 instead 3. I was seeing a better outcome with those (less failures) during with rolling upgrade. |
Do we need to update any other ones (int / ext /??) /test e2e-aws |
This is already getting the internal and external Kubernetes API balancers and the internal Ignition-config (machine-config server) load balancer. |
e2e-aws failed to build upi-installer image...
maybe retry |
/lgtm Will test over weekend in the CI and see the outcome in combo with the change to the wait period for shutdown |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: smarterclayton, wking 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 |
/hold cancel |
/retest |
@wking: The following test 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. 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. |
data/aws/vpc/master-elb: Set thresholds back to two
These were changes from two to three in 16dfbb3 (#594):
@crawford doesn't remember intentionally making that change, and the lower thresholds will hopefully help mitigate some issues with continued connection attempts to API servers which are in the process of shutting down.