Unable to easily follow the upgrade process

[juadk]

Setup

• Rancher version: 2.6.8
• Rancher-dashboard branch: elemental-dev

Describe the bug

Context: Test upgrade in the UI

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

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

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:

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

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]

FYI @nwmac @kwwii @agracey

[juadk]

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....

[agracey]

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]

@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]

Which information would be relevant to a user?

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

• How many clusters are in the selector
• Per cluster:
  • How many nodes have been upgraded / How many nodes left
  • Which node is being upgraded now
• Any Errors or Rollbacks that happened (globally)

[agracey]

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