Skip to content

e2e case: should not update any resources when service config is not changed is flaky #9736

@nilo19

Description

@nilo19

Which jobs are flaking:

e2e case: should not update any resources when service config is not changed is flaky due to etag mismatch.
example: https://prow.k8s.io/view/gs/kubernetes-ci-logs/pr-logs/pull/kubernetes-sigs_cloud-provider-azure/9723/pull-cloud-provider-azure-e2e-ccm-vmss-capz-1-33/1997713874370957312

Which test(s) are flaking:

Testgrid link:

Reason for failure:

Anything else we need to know:

  • links to go.k8s.io/triage appreciated
  • links to specific failures in spyglass appreciated

Metadata

Metadata

Assignees

No one assigned

    Labels

    kind/flakeCategorizes issue or PR as related to a flaky test.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions