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

Failed to run clusterctl move due failing to get API group resources #11808

Closed
cprivitere opened this issue Feb 5, 2025 · 3 comments
Closed
Labels
kind/flake Categorizes issue or PR as related to a flaky test. needs-priority Indicates an issue lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.

Comments

@cprivitere
Copy link
Member

Which jobs are flaking?

  • periodic-cluster-api-e2e-release-1-7
  • periodic-cluster-api-e2e-mink8s-release-1-8
  • periodic-cluster-api-e2e-release-1-8

Which tests are flaking?

Since when has it been flaking?

First spotted instance was on 1/1 at 3:48 AM - https://prow.k8s.io/view/gs/kubernetes-ci-logs/logs/periodic-cluster-api-e2e-release-1-7/1874391857312567296

Testgrid link

https://storage.googleapis.com/k8s-triage/index.html?date=2025-02-05&text=failed%20to%20get%20API%20group%20resources&job=.*cluster-api.*(test%7Ce2e)*&xjob=.*-provider-.*

Reason for failure (if possible)

Failed to run clusterctl move
Expected success, but got an error:
<...>
failed to get API group resources: unable to retrieve the complete list of server APIs....

Anything else we need to know?

These seem to me to be separate from #11162, which is an issue with machinepools. But I could be wrong.

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-priority Indicates an issue lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one. labels Feb 5, 2025
@k8s-ci-robot
Copy link
Contributor

This issue is currently awaiting triage.

If CAPI contributors determine this is a relevant issue, they will accept it by applying the triage/accepted label and provide further guidance.

The triage/accepted label can be added by org members by writing /triage accepted in a comment.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes-sigs/prow repository.

@cprivitere
Copy link
Member Author

A suggestion was made on slack to close this if it's really only affecting 1.8 and older. Which I'd be ok with.

@cprivitere
Copy link
Member Author

/close

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/flake Categorizes issue or PR as related to a flaky test. needs-priority Indicates an issue lacks a `priority/foo` label and requires one. needs-triage Indicates an issue or PR lacks a `triage/foo` label and requires one.
Projects
None yet
Development

No branches or pull requests

2 participants