-
Notifications
You must be signed in to change notification settings - Fork 192
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
NE-585: Make ROUTER_BACKEND_CHECK_INTERVAL configurable #712
NE-585: Make ROUTER_BACKEND_CHECK_INTERVAL configurable #712
Conversation
eeb2ed5
to
7111096
Compare
/retest |
da7698d
to
8928044
Compare
/retest |
1 similar comment
/retest |
/test e2e-aws |
/retest |
The e2e test for componentRoutes could use tweaking if this comes up frequently: /retest |
8928044
to
40e3112
Compare
/retest |
dd2bb4c
to
df7d2b8
Compare
Interesting failure:
/retest |
df7d2b8
to
ea5f804
Compare
/retest |
1 similar comment
/retest |
c306d56
to
b35f5c4
Compare
could not run steps: step e2e-aws failed: failed to acquire lease for "aws-quota-slice": resources not found |
8267ef0
to
1d6bfc2
Compare
/retest |
|
/retest |
Again:
/retest |
Try bumping openshift/api to openshift/api@716dc56 or newer. |
test/e2e/checkinterval_test.go
Outdated
// when set to an unacceptable value, it should not be accepted | ||
if err := waitForDeploymentEnvVar(t, kclient, routerDeployment, deploymentTimeout, ingresscontroller.RouterBackendCheckInterval, (0 * time.Second).String()); err == nil { | ||
t.Fatalf("unexpected router deployment %s set at %v: %v", ingresscontroller.RouterBackendCheckInterval, 2*defaultHealthCheckInterval, err) | ||
} | ||
|
||
// when set to an unacceptable value, the env variable should not exist | ||
if err := waitForDeploymentEnvVar(t, kclient, routerDeployment, deploymentTimeout, ingresscontroller.RouterBackendCheckInterval, ""); err != nil { | ||
t.Fatalf("expected router deployment to remove %s: %v", ingresscontroller.RouterBackendCheckInterval, err) | ||
} |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Are both waitForDeploymentEnvVar
calls necessary? It seems like the second one (make sure the environment variable is absent) would suffice, and the first one (make sure the environment variable isn't set to an unexpected value) is superfluous.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
ok
c2d53f2
to
6c51354
Compare
/test e2e-aws-operator |
bf72dde
to
24de4a9
Compare
24de4a9
to
2849fcf
Compare
/lgtm |
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: candita, Miciah 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 |
/label qe-approved |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
2 similar comments
/retest-required Please review the full test history for this PR and help us cut down flakes. |
/retest-required Please review the full test history for this PR and help us cut down flakes. |
We might need to add a retry around the update in that test. |
@candita: all tests passed! Full PR test history. Your PR dashboard. 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. |
NE-585 Expose and make configurable ROUTER_BACKEND_CHECK_INTERVAL to customize the length of time between subsequent liveness checks on backends. Details in the enhancement proposal
Refactor some unit tests and add e2e test.