periodics and propably presubmit tests fail while a release is tagged but not yet published #10450
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.
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:
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.
The text was updated successfully, but these errors were encountered: