Public projects are not being displayed.

We have GitLab set up internally (v 9.0.5). 40 private projects have been made public. When a new user logs into GitLab, there is a section at the bottom of their screen which says:

There are 40 public projects on this server. Public projects are an easy way to allow everyone to have read-only access.

They click on the "Browse projects" button.

The next page comes up with "No projects found."

Is there a configuration issue with the new user? The 40 repositories have their visibility set to "Public" and the repository, merge requests, and pipelines are all set to "Everyone with access."

What's missing?

moved from gitlab-com/support-forum#1747 (closed)

@jfota I transferred this issue to the GitLab CE issue tracker as the tracker where the issue was originally posted is for issues relating to the GitLab.com platform.

@jfota That does sound like the incorrect behaviour. We'll need to check the projects that the user is permitted to see via the Rails console to identify the problem here:

Open the rails console:

sudo gitlab-rails console

Query the visible projects for that user:

username = 'git'

user = User.find_by_username(username)
user.authorized_projects.count
user.authorized_projects.map(&:name_with_namespace)

refresh_service = Users::RefreshAuthorizedProjectsService.new(user)
fresh_auths = refresh_service.fresh_authorizations
fresh_auths.map(&:project).count
fresh_auths.map(&:project).map(&:name_with_namespace)

Hi, I have a problem that is very similar to @jfota's. Some user reported that she can only see 2 projects on her dashboard, but she owns 5 and has been granted access to 3 more. She gets 404 Not Found if she tries to access URL of any "missing" project manually. I have verified this behavior using Impersonate function.

What's weird is that I can see all her projects in /admin/users/login and the complete list is returned as well via GitLab API.

The query you posted above returns 2 for user.authorized_projects.count and 8 for fresh_auths.map(&:project).count. I tried to google for a while and came upon gitlab-rake gitlab:user:check_repos[login], which only checked the 2 projects.

Our GitLab version is 9.1.1 (d3123f67).

I've run the commands you listed, but I not sure how to interpret the results.

irb(main):037:0* user = User.find_by_username(username) => #<User id: 34, email: "ibenninghoff@maprtech.com", created_at: "2017-04-14 19:25:06", updated_at: "2017-05-01 17:37:07", name: "John Benninghoff", admin: false, projects_limit: 17, skype: "", linkedin: "", twitter: "", authentication_token: "kxy5HmDLfowExfAE5dZh", bio: nil, username: "ibenninghoff", can_create_group: true, can_create_team: false, state: "active", color_scheme_id: 1, password_expires_at: nil, created_by_id: nil, last_credential_check_at: "2017-05-01 17:37:07", avatar: nil, hide_no_ssh_key: false, website_url: "", notification_email: "ibenninghoff@maprtech.com", hide_no_password: false, password_automatically_set: true, location: nil, encrypted_otp_secret: nil, encrypted_otp_secret_iv: nil, encrypted_otp_secret_salt: nil, otp_required_for_login: false, otp_backup_codes: nil, public_email: "", dashboard: 0, project_view: 2, consumed_timestep: nil, layout: 0, hide_project_limit: false, otp_grace_period_started_at: nil, ldap_email: true, external: false, organization: nil, incoming_email_token: "etr4dhs69h1n3cl1cise8bvz5", authorized_projects_populated: true, ghost: nil, require_two_factor_authentication_from_group: false, two_factor_grace_period: 48, last_activity_on: nil, notified_of_own_activity: nil> irb(main):038:0> user.authorized_projects.count => 0 irb(main):039:0> user.authorized_projects.map(&:name_with_namespace) => [] irb(main):040:0> refresh_service = Users::RefreshAuthorizedProjectsService.new(user) => #<Users::RefreshAuthorizedProjectsService:0x007fa078c41a10 @user=#<User id: 34, email: "ibenninghoff@maprtech.com", created_at: "2017-04-14 19:25:06", updated_at: "2017-05-01 17:37:07", name: "John Benninghoff", admin: false, projects_limit: 17, skype: "", linkedin: "", twitter: "", authentication_token: "kxy5HmDLfowExfAE5dZh", bio: nil, username: "ibenninghoff", can_create_group: true, can_create_team: false, state: "active", color_scheme_id: 1, password_expires_at: nil, created_by_id: nil, last_credential_check_at: "2017-05-01 17:37:07", avatar: nil, hide_no_ssh_key: false, website_url: "", notification_email: "ibenninghoff@maprtech.com", hide_no_password: false, password_automatically_set: true, location: nil, encrypted_otp_secret: nil, encrypted_otp_secret_iv: nil, encrypted_otp_secret_salt: nil, otp_required_for_login: false, otp_backup_codes: nil, public_email: "", dashboard: 0, project_view: 2, consumed_timestep: nil, layout: 0, hide_project_limit: false, otp_grace_period_started_at: nil, ldap_email: true, external: false, organization: nil, incoming_email_token: "etr4dhs69h1n3cl1cise8bvz5", authorized_projects_populated: true, ghost: nil, require_two_factor_authentication_from_group: false, two_factor_grace_period: 48, last_activity_on: nil, notified_of_own_activity: nil>> irb(main):041:0> fresh_auths = refresh_service.fresh_authorizations => #<ActiveRecord::Relation []> irb(main):042:0> fresh_auths.map(&:project).count => 0 irb(main):043:0> fresh_auths.map(&:project).map(&:name_with_namespace) => []

@roman.lacko921 Your results are what I would have expected. You can resolve your problem with the following command:

username = 'git'

user = User.find_by_username(username)
user.refresh_authorized_projects

We have made some changes in this area and I hope that this is only one user that was experiencing this issue before your upgrade to 9.1.1.

To be sure that all users are picked up, maybe we should run through and refresh the authorizations across users on your instance:

User.all.each(&:refresh_authorized_projects)

Please let us know how that goes.

@jfota Please can you run another test from the Rails console for this user:

username = 'git'

user = User.find_by_username(username)
public_projects_for_user = Project.public_to_user(user); nil
public_projects_for_user.count
public_projects_for_user.map(&:name_with_namespace)

Please carry out the same test for your own user and the affected user.

@markglenfletcher I've run the command for all users and the affected user can finally see all her projects in the dashboard (at least via Impersonate function). Thank you very much.

@roman.lacko921 Thanks for the update. Please raise another issue if you see problems since upgrading to 9.1.1

I ran the commands. No change from what I reported. According to the public_projects_for_user.count, there should be 45 public projects I should be able to browse, but when I click on the "Browse Projects" button I still see "No Projects Found".

If the VisibilityLevel::public_to_user method is returning the 45 projects, then they should be displayed in the explore projects list. I can't see anywhere that the result of the query, or the views, is cached so I don't think that this is the issue but can you try clearing the cache just in case?

sudo gitlab-rake cache:clear

No joy.

Is there anything different about this particular user? Are other new users also experiencing the same problems?

Nothing I can see. I impersonated 4 other users, all 4 showed 45 public repos and all 4 yielded "No projects found."

Do non-authenticated visitors have the same issue? Can you log out and check or check in an incognito/private window?

If I understand your response, all users are authenticated via LDAP.

Because these projects are public they should be accessible to users that have not logged in to. Is this the case when you visit the /explore without logging in or are the projects missing there too?

Only one of the 45 projects is public when I go to /explore.

moved to gitlab#9368

Hey!

GitLab is moving all development for both GitLab Community Edition and Enterprise Edition into a single codebase. The current gitlab-ce repository will become a read-only mirror, without any proprietary code. All development is moved to the current gitlab-ee repository, which we will rename to just gitlab in the coming weeks. As part of this migration, issues will be moved to the current gitlab-ee project.

If you have any questions about all of this, please ask them in our dedicated FAQ issue.

https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

You can also find more information here:

• https://gitlab.com/gitlab-org/gitlab-ee/issues/13304
• https://about.gitlab.com/2019/08/23/a-single-codebase-for-gitlab-community-and-enterprise-edition/

Frequently Asked Questions

For an up to date list of questions and answers, please take a look at https://gitlab.com/gitlab-org/gitlab-ee/issues/13855

What will we do with the repository names?

https://gitlab.com/gitlab-org/gitlab-ee/ will become https://gitlab.com/gitlab-org/gitlab, and https://gitlab.com/gitlab-org/gitlab-ce will become https://gitlab.com/gitlab-org/gitlab-foss.

Why rename gitlab-ce to gitlab-foss?

Using "gitlab" and "gitlab-ce" would be confusing, so we decided to rename gitlab-ce to gitlab-foss to make the purpose of this FOSS repository more clear

I created a merge requests for CE, and this got closed. What do I need to do?

You will need to create a merge request at https://gitlab.com/gitlab-org/gitlab-ee/. This link will eventually redirect to https://gitlab.com/gitlab-org/gitlab.

How does the licensing work in this new setup?

Everything in the ee/ directory is proprietary. Everything else is free and open source software. If your merge request does not change anything in the ee/ directory, the process of contributing changes is the same as when using the gitlab-ce repository.

Will you accept merge requests on the gitlab-ce/gitlab-foss project after it has been renamed?

No. Merge requests submitted to this project will be closed automatically.

Will I still be able to view old issues and merge requests in gitlab-ce/gitlab-foss?

Yes.

How will this affect users of GitLab CE using Omnibus?

No changes will be necessary, as the packages built remain the same.

How will this affect users of GitLab CE that build from source?

Once the project has been renamed, you will need to change your Git remotes to use this new URL. GitLab will take care of redirecting Git operations so there is no hard deadline, but we recommend doing this as soon as the projects have been renamed.

Where can I see a timeline of the remaining steps?

https://gitlab.com/gitlab-org/gitlab-ee/issues/13304

Will community contributions submitted to the new "gitlab" repository be available in the new gitlab-foss repository?

Yes, these changes will be synced to gitlab-foss automatically, several times per day.

locked this issue