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
When a user tries to "clone" a namespace (ns 1) in the UI, it does not clone the metadata annotation that sets the project that the namespace (ns 1) it is cloning is in. Therefore, after creating the namespace (ns 2), users who only have access to the project of the namespace (ns 1) they cloned can no longer see the cloned namespace (ns 2) and cannot move it to the project that they have access to.
Troubleshooting steps:
When copying the namespace, a user can edit the YAML and paste in the annotation containing the projectId of the project they would like assigned. EX:
The cloned namespace is put in "not in a project", but user can see it.
The user tries to move the namespace to the project they have access to, but it errors out.
If the user refreshes or logs out/in they can no longer see the cloned namespace.
Workaround:
When copying the namespace, a user can edit the YAML and paste in the annotation containing the projectId of the project they would like assigned, like so:
As u1, create a downstream rke1 or rke2 cluster - cluster type does not matter.
Add u2 as a cluster member in the downstream clusters.
As u2, create 2 projects P1 and P2
In P1, create a namespace ns1
From ns1, clone a new namespace - cloned ns gets created in Not in a project
Move the ns from Not in a project to the project P1
Throws a forbidden error as the project owner does not have access to Not in a project
Verified on v2.7-head 2b2ed44
Create a rancher server on v2.7.0
Create 2 standard users - u1 and u2
As u1, create a downstream rke1 or rke2 cluster - cluster type does not matter.
Add u2 as a cluster member in the downstream clusters.
As u2, create 2 projects P1 and P2
In P1, create a namespace ns1
From ns1, clone a new namespace - cloned ns gets created in project P1
Repeated the above steps as a cluster member and works as expected.
Note:
If we move any namespace from one project to another project as a cluster member/project owner - unable to create deployments in that namespace as mentioned in the linked ticket above.
Internal reference: SURE-5408
Reported in 2.6.7
When a user tries to "clone" a namespace (ns 1) in the UI, it does not clone the metadata annotation that sets the project that the namespace (ns 1) it is cloning is in. Therefore, after creating the namespace (ns 2), users who only have access to the project of the namespace (ns 1) they cloned can no longer see the cloned namespace (ns 2) and cannot move it to the project that they have access to.
Troubleshooting steps:
When copying the namespace, a user can edit the YAML and paste in the annotation containing the projectId of the project they would like assigned. EX:
Repro steps:
Workaround:
When copying the namespace, a user can edit the YAML and paste in the annotation containing the projectId of the project they would like assigned, like so:
Actual behavior:
Cloned namespace does not clone the project of the namespace being cloned.
Expected behavior:
Cloned namespace is placed in the same project as the namespace being cloned.
The text was updated successfully, but these errors were encountered: