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
In Rancher 2.9-head, clusters in Fleet display status not ready even when they are.This happens for both fleet-local and fleet-default and it was working fine in previous versions:
Taking a look at clusters.fleet.cattle.io it seems Nodes Ready are missing in 2.9-head (fleet:v0.10.0-rc.11)
→ k get clusters.fleet.cattle.io -n fleet-local local
NAME BUNDLES-READY LAST-SEEN STATUS
local 1/1 2024-04-17T05:05:37Z
→ k describe clusters.fleet.cattle.io -n fleet-local local | grep "Ready Nodes"
→
...while this is ok in Rancher 2.8.3 with fleet:v0.9.2:
➜ ~ k get clusters.fleet.cattle.io -n fleet-local local
NAME BUNDLES-READY NODES-READY SAMPLE-NODE LAST-SEEN STATUS
local 1/1 1/1 mmartinsuse 2024-04-17T05:03:56Z
➜ ~ k describe clusters.fleet.cattle.io -n fleet-local local | grep "Ready Nodes"
Non Ready Nodes: 0
Ready Nodes: 1
Ready Nodes: 1/1
Here you can see full info on yamls for both versions:
To summarize, clusters.fleet.cattle.io resource in v0.10 doesn't contain status.agent.readyNodes object anymore which is probably mandatory for rancher UI.
Issue
In
Rancher 2.9-head
, clusters in Fleet display status not ready even when they are.This happens for bothfleet-local
andfleet-default
and it was working fine in previous versions:Taking a look at
clusters.fleet.cattle.io
it seemsNodes Ready
are missing in 2.9-head (fleet:v0.10.0-rc.11
)...while this is ok in Rancher 2.8.3 with
fleet:v0.9.2
:Here you can see full info on yamls for both versions:
notreadynodesinstatus_290.yaml
readynodesinstatus_283.yaml
Let's please return this value so the UI can correctly reflect this value
Test steps / environment
Rancher v2.8.3
/Fleet 0.9.2
and2.9-head
(v2.9-0dc6561b4a0cbcda67199cf86d45d28da10ac1f5-head
) /fleet:v0.10.0-rc.11
K3S_VERSION=v1.27.10+k3s1
Observed behavior:
0
inRancher v2.9-head
and1
inRancher v2.8.3
The text was updated successfully, but these errors were encountered: