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.

Sign up for GitHub

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

Jump to bottom

[backport v2.10.1] RKE2 Clusters are incorrectly treated as imported clusters while they are provisioning #12663

Open
github-actions bot opened this issue Nov 25, 2024 · 0 comments
Open

[backport v2.10.1] RKE2 Clusters are incorrectly treated as imported clusters while they are provisioning #12663

github-actions bot opened this issue Nov 25, 2024 · 0 comments
Labels
kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this QA/None
Milestone
v2.10.1

Comments

@github-actions
Copy link
Contributor

This is a backport issue for #12662, automatically created via GitHub Actions workflow initiated by @mantis-toboggan-md

Original issue body:

image

Early investigation: The provider column is determined by management cluster status.provider and status.driver - it looks like driver is not populated until the cluster finishes provisioning. We probably need a better way of computing the mgmt cluster provider

Need to ensure we don't re-introduce
#12506
#12339
@github-actions github-actions bot added kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this QA/None labels Nov 25, 2024
@github-actions github-actions bot added this to the v2.10.1 milestone Nov 25, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees
No one assigned
Labels
kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this QA/None
Projects
None yet
Milestone
v2.10.1
Development

No branches or pull requests
0 participants