Namespace is not valid
Summary
New personal project creation, under user's own personal profile, throws "Namespace is not valid" errors for type:external users.
Steps to reproduce
- Deploy GitLab version 12.8.x to GKE using Helm chart.
- Create an LDAP integration to Microsoft Azure.
- Add LDAP group to "external_groups" list in Helm chart values file.
- Log in to GitLab, navigate to personal profile page and try to create a personal project. This works.
- Upgrade GitLab by deploying GitLab version 12.10.1 to GKE using Helm chart 3.3.1
- Log in to GitLab, navigate to personal profile page and try to create a personal project. This doesn't work!!!
What is the current bug behavior?
At the moment, when trying to create a personal project as an external user, you're met with "Namespace not valid" error.
What is the expected correct behavior?
As explained here, external users cannot create groups, projects, or personal snippets but they should be able to create personal projects.
This was working on GitLab version 12.8.x
Relevant logs and/or screenshots
Please see the attached screenshots.
Output of checks
This bug happens on GitLab on GKE.
GitLab environment info
- GKE version 1.15.9-gke.24
- Helm chart version 3.3.1
- GitLab version 12.10.1-ee
Possible fixes
N/A
Edited by Michael Wetthasinghe