Thanks to visit codestin.com
Credit goes to github.com

Skip to content

Namespace not available to project member as soon as it gets created. #13703

@sangeethah

Description

@sangeethah

**Rancher versions: v2.0.2
Steps to Reproduce:
Create a "standard user"
Create a project and assign this "standard user" as member to this project.
Log in as this user.
Go to project page and create a workload by specifying a new namespace.

Sometimes , workload creation fails with deployments.apps is forbidden: User “u-588pc” cannot create deployments.apps in the namespace “test34": Unknown user “u-588pc”

When "launch" button is clicked again, workload creation succeeds.

In the automation scripts , When a project member/cluster member creates a new namespace and then tries to query for the namespace immediately , namespace is not listed. If we wait for 1-2 seconds and query for the namespace it gets listed.

Edit from Craig:
Note that this bug is a race condition, so you may need to try multiple times to reproduce. Seems like if you try 10 times and don't see it, that should be sufficient. You DONT need to create a user for each iteration. You can reuse the same user, you just need to create a new workload specifying a new namespace using the "Add to new namespace" option every time.

Metadata

Metadata

Labels

kind/bugIssues that are defects reported by users or that we know have reached a real release

Type

No type

Projects

No projects

Milestone

Relationships

None yet

Development

No branches or pull requests

Issue actions