Skip to content
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

periodics and propably presubmit tests fail while a release is tagged but not yet published #10450

Closed
chrischdi opened this issue Apr 17, 2024 · 3 comments · Fixed by #10618
Closed
Assignees
Labels
area/e2e-testing Issues or PRs related to e2e testing help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/flake Categorizes issue or PR as related to a flaky test. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.

Comments

@chrischdi
Copy link
Member

chrischdi commented Apr 17, 2024

Which jobs are flaking?

All periodics of the release which is to-be cut, e.g.:

https://storage.googleapis.com/k8s-triage/index.html?date=2024-04-20&text=The%20first%20SynchronizedBeforeSuite%20function%20running%20on%20Ginkgo%20parallel%20process%7C%20got%20status%20code%20404&job=.*-cluster-api-.*&xjob=.*-provider-.*%7C.*-operator-

Also affects providers which use the marker tooling

Which tests are flaking?

periodic-cluster-api-e2e-mink8s-release-1-7
periodic-cluster-api-e2e-conformance-ci-latest-release-1-7
periodic-cluster-api-e2e-conformance-release-1-7
periodic-cluster-api-e2e-dualstack-and-ipv6-release-1-7
periodic-cluster-api-e2e-release-1-7

Since when has it been flaking?

The time between:

  • tag for the release got created
  • until release (and by that the artifacts) got published

Testgrid link

No response

Reason for failure (if possible)

Release marker resolved to the tag but it was not yet published.

Anything else we need to know?

This is similar to

Label(s) to be applied

/kind flake
One or more /area label. See https://github.com/kubernetes-sigs/cluster-api/labels?q=area for the list of labels.

@k8s-ci-robot k8s-ci-robot added kind/flake Categorizes issue or PR as related to a flaky test. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Apr 17, 2024
@chrischdi
Copy link
Member Author

chrischdi commented Apr 17, 2024

The feature got introduced in:

It could propably be solved similar to:

@sbueringer sbueringer added the area/e2e-testing Issues or PRs related to e2e testing label Apr 17, 2024
@fabriziopandini fabriziopandini added priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. triage/accepted Indicates an issue or PR is ready to be actively worked on. labels Apr 18, 2024
@k8s-ci-robot k8s-ci-robot removed the needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. label Apr 18, 2024
@chrischdi
Copy link
Member Author

xref: occurency from today: https://prow.k8s.io/view/gs/kubernetes-jenkins/pr-logs/pull/kubernetes-sigs_cluster-api/10613/pull-cluster-api-e2e-blocking-main/1790422497817006080

@chrischdi
Copy link
Member Author

/assign

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
area/e2e-testing Issues or PRs related to e2e testing help wanted Denotes an issue that needs help from a contributor. Must meet "help wanted" guidelines. kind/flake Categorizes issue or PR as related to a flaky test. priority/important-longterm Important over the long term, but may not be staffed and/or may need multiple releases to complete. triage/accepted Indicates an issue or PR is ready to be actively worked on.
Projects
None yet
4 participants