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

Fleet status shows error for an imported cluster #10738

Closed
nwmac opened this issue Apr 2, 2024 · 1 comment · Fixed by #10755
Closed

Fleet status shows error for an imported cluster #10738

nwmac opened this issue Apr 2, 2024 · 1 comment · Fixed by #10755
Assignees
Labels
kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this size/3 Size Estimate 3
Milestone

Comments

@nwmac
Copy link
Member

nwmac commented Apr 2, 2024

Create a cluster and then import it into Rancher.

The new Fleet status always shows an error.

It looks like for an imported cluster, the fleet agent is a StatefulSet and not a Deployment, so we are failing to find it.

I also don't see the cluster agent status for an imported Cluster.

@nwmac nwmac added the kind/bug label Apr 2, 2024
@nwmac nwmac added this to the v2.9.0 milestone Apr 2, 2024
@github-actions github-actions bot added [zube]: To Triage QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this labels Apr 2, 2024
@nwmac nwmac added [zube]: Backlog and removed [zube]: To Triage QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this labels Apr 2, 2024
@gaktive gaktive added QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this size/3 Size Estimate 3 [zube]: Groomed and removed [zube]: Backlog labels Apr 3, 2024
@richard-cox
Copy link
Member

richard-cox commented Apr 3, 2024

I've seen this in a DO RKE2 cluster as well. dashboard fleet icon shows error, fleet-agent was a statefulset.

Note - We should be considerate of scaling issues when fetching stateful sets. Ideally we should attempt to fetch the specific one if we can work out the id

Edit:

  • local cluster
    • deployment - cattle-fleet-system/fleet-controller
    • statefulset - cattle-fleet-local-system/fleet-agent
  • downstream rke2
    • no deployment
    • statefulset - cattle-fleet-system/fleet-agent

Wondering if we should check both deployment and stateful set for upstream clusters, and stateful set in other namespace for downstream clusters?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this size/3 Size Estimate 3
Projects
None yet
Development

Successfully merging a pull request may close this issue.

4 participants