You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
when a user creates a custom rke1 cluster, they are shown an iframe page from ember with the registration options. However, once they click away from that page, the only way to get back to the registration page is to select the cluster -> registration tab. This page shows the vue page instead. There is mismatching information i.e. for this ticket, the windows warning only shows up in the vue page.
To Reproduce
deploy a custom rke1 cluster
Result
user is brought to an ember page upon creating the cluster
Expected Result
I would expect consistency. I believe the right approach would be to bring the user to the vue page showing the cluster -> registration page instead of the ember page
Screenshots
ember page:
vue page:
The text was updated successfully, but these errors were encountered:
Setup
Describe the bug
when a user creates a custom rke1 cluster, they are shown an iframe page from ember with the registration options. However, once they click away from that page, the only way to get back to the registration page is to select the cluster -> registration tab. This page shows the vue page instead. There is mismatching information i.e. for this ticket, the windows warning only shows up in the vue page.
To Reproduce
deploy a custom rke1 cluster
Result
user is brought to an ember page upon creating the cluster
Expected Result
I would expect consistency. I believe the right approach would be to bring the user to the vue page showing the cluster -> registration page instead of the ember page
Screenshots
ember page:
![Screen Shot 2022-08-11 at 9 28 39 AM](https://user-images.githubusercontent.com/16691014/184183448-86debcc6-701a-43fa-9da8-293947f48381.png)
vue page:
![Screen Shot 2022-08-11 at 9 28 46 AM](https://user-images.githubusercontent.com/16691014/184183476-c41bc390-39d8-4dfc-90e8-1b60317d145b.png)
The text was updated successfully, but these errors were encountered: