search

rancher / elemental-ui

Rancher UI Plugin for Elemental
Apache License 2.0
12 stars 11 forks source link

Unable to easily follow the upgrade process #1

Open juadk opened 2 years ago

juadk commented 2 years ago

Setup

Describe the bug

Context: Test upgrade in the UI

When you upgrade a node, there is no easy way to follow the process: image

You can see that the upgrade process has been created but you don't really know what happens. image

If you want to follow a little bit more, you have to go to the Dashboard in the Elemental UI and click on Manage Elemental Cluster: image

Then, you will see your cluster's status changed, switch from active to error to updating and then back to active. image

From my point of view, we need a better way to track upgrades.

To Reproduce

  1. Setup Rancher and navigate to OS Management.
  2. Create a machine registration and a machine inventory, according to your specifications.
  3. Once done, head to OS Management > Dashboard > Create Elemental Cluster.
  4. Once the cluster ok, create an OS Image Upgrades and the upgrade will start in background
aalves08 commented 2 years ago

FYI @nwmac @kwwii @agracey

juadk commented 2 years ago

It could also make sense to have a way to check if the node is booted from the expecting image. Because right now, I cannot see an other solution than checking the/etc/os-release file with a ssh command.... image

agracey commented 2 years ago

I think this is a really good feature to have!

How do we follow the process of an upgrade of k3s? I would imagine the UX should be the same.

kwwii commented 2 years ago

@agracey This UI follows the standard pattern used to display the status of kubernetes resources in the Rancher Manager UI. Which information would be relevant to a user? Does the back-end provide that level of detail? This sounds like a feature which needs definition and planning, not a "bug".

agracey commented 2 years ago

Which information would be relevant to a user?

Off the top of my head but I'm sure there are more:

agracey commented 2 years ago

I don't think the backend does provide that data (yet...) so we would need to define the flow and open a ticket there.