Similarly to #26417 (closed) after recent updates (i believe 8.15) project permissions do not get inherited from group and it affects only new projects.
Projects created before the update continue to work fine.
So I have:
in Group level a developer with Developer permissions
it should inherited to Project Members. and visually it is so
the developer does not have Developer permissions in Project
i assign the same developer Developer privileges to Project, developer gets Developer access
some kind of inheritance broken for newly created projects?
Designs
Child items
...
Show closed items
Linked items
0
Link issues together to show that they're related or that one is blocking others.
Learn more.
If these can not be applied for whatever reason the easiest way of solving this problem for a specific user is to run the following in a Rails console:
I just upgraded to 8.16.3, then 8.16.4 and have a similar problem.
Basically master can add private projects on private groups but is then unable to acces them.
Steps to recreate:
owner creating a private group
owner adds a master user
master creates private project in private group
project is created, master is redirected from new project dialog to new project dashboard
master hits a 404 page (although he should have inherited master permissions on new private project)
reloading page keeps bringing up 404
owner though, can access the project page
owner gives owner permissions to master user (on group) (-> owner2)
owner2 (former master) can now access the project page
Get empty list. No developers inside this project.
After execution of command by @yorickpeterse problem have gone. But it's not ok to execute this command each time we create new project for each developer. Is there any ultimate solution?
@br0ke This work happens in a deferred background job. You can check to see if these jobs are being scheduled and executed by tailing GitLab's log files:
sudo gitlab-ctl tail
Then add the new project to the group
You should see AuthorizedProjectsWorker items in the sidekiq logs for each group member:
@br0ke Have you seen any other issues with background work, like events or comments not being created? It would be good to see the activity in the logs at the time of these tests.
@markglenfletcher I can add comments to issues, it's working well. Did not test events yet.
I performed following actions:
Create new project 'test_gitlab_3' inside of our group;
Create issue 'test issue';
Write a few comments.
Here I attach gitlab-ctl tail output at the time of these tests (replaced some usernames and IPs in logs with placeholders). I tried to make this logs as small as possible so did it fast (~30 sec). You can find my activity in logs by my username 'semakin'.