-
Notifications
You must be signed in to change notification settings - Fork 443
disable external load balancer test #1123
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
Conversation
Expect(resp.StatusCode).To(Equal(200)) | ||
Expect(err).NotTo(HaveOccurred()) | ||
} | ||
// TODO: determine root issue of failures of addressing the ELB from prow and fix |
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.
was deferring the delete not enough?
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.
No. Deferring was not enough. :(
We still run test the elb through the curl job and it succeeds, so at least we are not 100% blind.
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.
/lgtm
/approve
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: CecileRobertMichon 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 |
Unrelated failure:
|
/retest |
the IPv6 flake has been around for a while, doesn't happen super often :( |
What type of PR is this?
/kind failing-test
What this PR does / why we need it:
Tests are failing for load balancers and it seems to happen when the cloud provider removes an internal load balancer from a VMSS and then quickly tries to update the VMSS with another load balancer. This PR disables the external load balancer test which tests connectivity from outside of the cluster. We still verify connectivity from a curl job inside of the cluster. A TODO has been added to re-enable.
Additional work is being done here: #1121
Special notes for your reviewer:
Please confirm that if this PR changes any image versions, then that's the sole change this PR makes.
TODOs:
Release note: