https://rancher.com/ logo
#general
Title
# general
a

adamant-kite-43734

11/01/2022, 8:31 PM
This message was deleted.
h

hundreds-state-15112

11/01/2022, 8:32 PM
I have used the Rancher Backup operator so I can reset and restoring to 2.5.16 works fine I just can’t figure out what’s wrong with the upgrade?
I’ve googled the error and gotten anything from recreating expired webhooks (not the issue) to cloud provider bugs, but these use the custom node driver for RKE1
k3s 1.20.15, Rancher 2.5.16 -> 2.6.1, downstream clusters are k8s 1.18.12
Oh so using the Cluster Explorer I can get a slightly further glimpse at
This resource is currently in a transitioning state, but there isn’t a detailed message available.
Okay that helped me find this error in the bundle resources
Copy code
'rendered manifests contain a resource that already exists. Unable
to continue with install: could not get information about the resource:
<http://clusterroles.rbac.authorization.k8s.io|clusterroles.rbac.authorization.k8s.io> "cattle-fleet-system-fleet-agent-role"
is forbidden: User "system:serviceaccount:fleet-system:fleet-agent" cannot
get resource "clusterroles" in API group "<http://rbac.authorization.k8s.io|rbac.authorization.k8s.io>" at
the cluster scope: RBAC: <http://clusterrole.rbac.authorization.k8s.io|clusterrole.rbac.authorization.k8s.io> "fleet-system-fleet-agent-role"
not found'
Starting to think Rancher somehow installed more fleets than it needed? Can someone confirm?
Similar looking issue
So probably a fleet related issue
Cross posting
535 Views