Skip to content

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

Merged
merged 1 commit into from
Jan 16, 2021

Conversation

devigned
Copy link
Contributor

@devigned devigned commented Jan 15, 2021

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:

  • squashed commits
  • includes documentation
  • adds unit tests

Release note:

NONE

@k8s-ci-robot k8s-ci-robot added release-note-none Denotes a PR that doesn't merit a release note. kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. size/S Denotes a PR that changes 10-29 lines, ignoring generated files. area/provider/azure Issues or PRs related to azure provider labels Jan 15, 2021
@k8s-ci-robot k8s-ci-robot added the sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. label Jan 15, 2021
@devigned devigned changed the title defer internal load balancer clean up disable external load balancer test Jan 15, 2021
@k8s-ci-robot k8s-ci-robot added size/M Denotes a PR that changes 30-99 lines, ignoring generated files. and removed size/S Denotes a PR that changes 10-29 lines, ignoring generated files. labels Jan 15, 2021
Expect(resp.StatusCode).To(Equal(200))
Expect(err).NotTo(HaveOccurred())
}
// TODO: determine root issue of failures of addressing the ELB from prow and fix
Copy link
Contributor

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?

Copy link
Contributor Author

@devigned devigned Jan 15, 2021

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.

Copy link
Contributor

@CecileRobertMichon CecileRobertMichon left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

/lgtm
/approve

@k8s-ci-robot k8s-ci-robot added the lgtm "Looks good to me", indicates that a PR is ready to be merged. label Jan 15, 2021
@k8s-ci-robot
Copy link
Contributor

[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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@k8s-ci-robot k8s-ci-robot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Jan 15, 2021
@devigned
Copy link
Contributor Author

Unrelated failure:

INFO: "With ipv6 worker node" ran for 31m33s on Ginkgo node 3 of 3


�[91m�[1m• Failure [1893.108 seconds]�[0m
Workload cluster creation
�[90m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:39�[0m
  Creating a ipv6 control-plane cluster
  �[90m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:215�[0m
    �[91m�[1mWith ipv6 worker node [It]�[0m
    �[90m/home/prow/go/src/sigs.k8s.io/cluster-api-provider-azure/test/e2e/azure_test.go:216�[0m

    �[91mTimed out after 1200.000s.
    Expected
        <int>: 2
    to equal
        <int>: 3�[0m

@devigned
Copy link
Contributor Author

/retest

@nader-ziada
Copy link
Contributor

the IPv6 flake has been around for a while, doesn't happen super often :(

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. area/provider/azure Issues or PRs related to azure provider cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. kind/failing-test Categorizes issue or PR as related to a consistently or frequently failing test. lgtm "Looks good to me", indicates that a PR is ready to be merged. release-note-none Denotes a PR that doesn't merit a release note. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. size/M Denotes a PR that changes 30-99 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants