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

Vue3: Cluster Details: RKE1: Node state for newly provisioning cluster says Provisioning instead of Active #12194

Open
yonasberhe23 opened this issue Oct 9, 2024 · 4 comments · Fixed by #12171
Open

Vue3: Cluster Details: RKE1: Node state for newly provisioning cluster says Provisioning instead of Active #12194

yonasberhe23 opened this issue Oct 9, 2024 · 4 comments · Fixed by #12171
Assignees
@rak-phillip @yonasberhe23
Labels
area/vue3 Bugs and technical debts as outcome to the Vue3 migration kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Milestone
v2.10.0

Comments

@yonasberhe23
Copy link
Contributor

Setup

  • Rancher version: v2.10
  • Rancher UI Extensions:
  • Browser type & version: Chrome, Firefox

Describe the bug
The node state for a newly provisioning cluster says Provisioning instead of Active until the user refreshes the page.

To Reproduce

  1. create RKE1 cluster (AWS/Azure) OR add a node to an existing RKE1 cluster
  2. go to cluster details > Machine Pools tab
  3. wait for the provisioning process to complete (~9 minutes)
  4. state column says Provisioning
  5. refresh the page
  6. state column says Active

Result
The node state for a newly provisioning cluster says Provisioning instead of Active until page refresh.

Expected Result
The node state for a newly provisioning cluster says Active without refresh.

Screenshots

Screen.Recording.2024-10-05.at.11.22.10.AM.mov

Additional context
@yonasberhe23 yonasberhe23 added kind/bug area/vue3 Bugs and technical debts as outcome to the Vue3 migration labels Oct 9, 2024
@yonasberhe23 yonasberhe23 added this to the v2.10.0 milestone Oct 9, 2024
@github-actions github-actions bot added the QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this label Oct 9, 2024
@richard-cox
Copy link
Member

Possibly related to #12189

This was referenced Oct 10, 2024
Closed
Open
@rak-phillip rak-phillip self-assigned this Oct 15, 2024
@rak-phillip rak-phillip mentioned this issue Oct 17, 2024
Merged
7 tasks
@rak-phillip
Copy link
Member

I tested this and it looks to be fixed with #12171.

This was referenced Oct 17, 2024
Open
Merged
@yonasberhe23 yonasberhe23 self-assigned this Oct 17, 2024
@github-actions github-actions bot mentioned this issue Oct 18, 2024
Merged
7 tasks
@richard-cox
Copy link
Member

Reopening, @rak-phillip i think you tagged #12282 with the wrong issue

@richard-cox richard-cox reopened this Oct 18, 2024
@rak-phillip
Copy link
Member

That's correct, fixed

@richard-cox richard-cox reopened this Oct 18, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@rak-phillip rak-phillip

@yonasberhe23 yonasberhe23

Labels
area/vue3 Bugs and technical debts as outcome to the Vue3 migration kind/bug QA/dev-automation Issues that engineers have written automation around so QA doesn't have look at this
Projects
None yet
Milestone
v2.10.0
Development

Successfully merging a pull request may close this issue.

Update model reactivety richard-cox/dashboard
3 participants
@rak-phillip @richard-cox @yonasberhe23