https://rancher.com/ logo
Join Slack
Powered by
Hi all, I would like to ask whether anyone is expe...
# general
f
Hi all, I would like to ask whether anyone is experiencing an issue with application deployment via Rancher UI 2.14.2: 
failed to wait for roles to be populated
. For more details, I have attached the Markdown documentation:
rancher-failed-to-wait-for-roles.md
s
that looks like a ton of ai output. not sure half (more?) is relevant. what's the root issue?
f
Most of our namespaces are missing the required annotation, likely 
InitialRolesPopulated
. Should this be handled by Rancher, or should it be managed via a custom automation mechanism during provisioning or upgrade?
s
as in, what's the bug? what are you doing to create the error 
failed to wait for roles to be populated
?
h
if you have not looked at this, start here and make sure you're meeting the requirements ranchermanager.docs.rancher.com/getting-started/installation-and-upgrade/installation-requirements you're installing rancher on what kubernetes distribution and version
f
@stocky-account-63046 The issue has occurred during installation of helmchart via RancherUI:
Sorry guys, everything worked fine with version 2.13.2, I'm currently testing latest version and I noticed this behavior.
@hundreds-evening-84071 OS: RockyLinux 8.10 RKE2 - v1.35.6+rke2r1
h
sorry - I misunderstood your original post... I thought you were installing rancher but after re-reading, you are deploying an app via UI
f
yes, no problem 😉
s
what's on step one, is a project, namespace or neither requested? is a new namespace created?
f
Richard, pls read a readme which I enclosed into this chat, it seems that problem is also in rancher 2.14.3, required annotations missing in already existing namespaces. In version 2.13.2 everything seems to be fine.
s
ah, that information was missing from the readme. the namespace was an existing one, so i'm guessing it was selected in step 1 of the ui's wizard? how was the namespace added to the project?
f
Copy code
[root@auto056 ~]# kubectl get ns default -o json   | jq -r '.metadata.annotations | to_entries[] | "\(.key)=\(.value)"'
<http://cattle.io/status={%22Conditions%22:[{%22Type%22:%22ResourceQuotaInit%22,%22Status%22:%22True%22,%22Message%22:%22%22,%22LastUpdateTime%22:%222026-07-06T08:32:48Z%22}]}|cattle.io/status={"Conditions":[{"Type":"ResourceQuotaInit","Status":"True","Message":"","LastUpdateTime":"2026-07-06T08:32:48Z"}]}>
<http://field.cattle.io/projectId=local:p-79jt8|field.cattle.io/projectId=local:p-79jt8>
<http://lifecycle.cattle.io/create.namespace-auth=true|lifecycle.cattle.io/create.namespace-auth=true>
<http://np.rke2.io|np.rke2.io>=resolved

[root@auto056 ~]# helm ls -ncattle-system
NAME                            NAMESPACE       REVISION        UPDATED                                 STATUS          CHART                                   APP VERSION
rancher                         cattle-system   1               2026-07-06 10:32:06.69309535 +0200 CEST deployed        rancher-2.14.3+171                      v2.14.3
rancher-webhook                 cattle-system   2               2026-07-06 08:33:36.301754562 +0000 UTC deployed        rancher-webhook-109.0.3+up0.10.7        0.10.7
system-upgrade-controller       cattle-system   1               2026-07-06 08:34:16.48318785 +0000 UTC  deployed        system-upgrade-controller-109.0.2       v0.19.1
I'm expecting something like:
Copy code
[root@auto052 ~]# kubectl get ns default -o json   | jq -r '.metadata.annotations | to_entries[] | "\(.key)=\(.value)"'
<http://cattle.io/status={%22Conditions%22:[{%22Type%22:%22ResourceQuotaInit%22,%22Status%22:%22True%22,%22Message%22:%22%22,%22LastUpdateTime%22:%222026-07-06T06:37:26Z%22},{%22Type%22:%22InitialRolesPopulated%22,%22Status%22:%22True%22,%22Message%22:%22%22,%22LastUpdateTime%22:%222026-07-06T06:37:31Z%22}]}|cattle.io/status={"Conditions":[{"Type":"ResourceQuotaInit","Status":"True","Message":"","LastUpdateTime":"2026-07-06T06:37:26Z"},{"Type":"InitialRolesPopulated","Status":"True","Message":"","LastUpdateTime":"2026-07-06T06:37:31Z"}]}>
<http://field.cattle.io/projectId=local:p-l7gxn|field.cattle.io/projectId=local:p-l7gxn>
<http://lifecycle.cattle.io/create.namespace-auth=true|lifecycle.cattle.io/create.namespace-auth=true>
<http://np.rke2.io|np.rke2.io>=resolved
7 Views
Open in Slack
PreviousNext
Powered by