Skip to content

Failed to fetch roles error on custom roles page. Underlying 500 error for GraphQL

Everyone can contribute. Help move this issue forward while earning points, leveling up and collecting rewards.

Summary

User is shown "Failed to fetch roles" error when navigating to the custom role's settings page of the top-level group. A network tab observation in the browser shows that a GraphQL query returns a 503 error.

Steps to reproduce

  1. Visit https://gitlab.com/groups/[NAME]/-/settings/roles_and_permissions

Example Project

What is the current bug behavior?

User is shown "Failed to fetch roles" error when navigating to the custom role's settings page.

What is the expected correct behavior?

User should be able to view the custom roles of the namespace.

Relevant logs and/or screenshots

https://log.gprd.gitlab.net/app/r/s/xMMhW

Screenshot 2024-10-10 at 17.27.17.png

[
  getGroupMemberRoles,
  [FILTERED],
  query getGroupMemberRoles($fullPath: ID!) {
    group(fullPath: $fullPath) {
      id
      standardRoles {
        ...StandardRoles
        __typename
      }
      memberRoles {
        nodes {
          ...MemberRole
          detailsPath
          __typename
        }
        __typename
      }
      __typename
    }
  }

  fragment StandardRoles on StandardRoleConnection {
    nodes {
      name
      accessLevel
      membersCount
      detailsPath
      __typename
    }
    __typename
  }

  fragment MemberRole on MemberRole {
    id
    name
    description
    membersCount
    editPath
    __typename
  },
  {
    "operationName"=>"getGroupMemberRoles",
    "variables"=>"[FILTERED]",
    "query"=>"query getGroupMemberRoles($fullPath: ID!) {
      group(fullPath: $fullPath) {
         id
         standardRoles {
          ...StandardRoles
          __typename   
        }    
        memberRoles {
          nodes {
            ...MemberRole
            detailsPath
            __typename
          }
          __typename
        }
        __typename
      }
    }
    fragment StandardRoles on StandardRoleConnection {
      nodes {
        name
        accessLevel
        membersCount
        detailsPath
        __typename
      }
      __typename
    }
    fragment MemberRole on MemberRole {
      id
      name
      description
      membersCount
      editPath
      __typename
    }
  }
]

Output of checks

This bug happens on GitLab.com

Results of GitLab environment info

Expand for output related to GitLab environment info

(For installations with omnibus-gitlab package run and paste the output of: \\\`sudo gitlab-rake gitlab:env:info\\\`) (For installations from source run and paste the output of: \\\`sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production\\\`)

Results of GitLab application Check

Expand for output related to the GitLab application check

(For installations with omnibus-gitlab package run and paste the output of: \`sudo gitlab-rake gitlab:check SANITIZE=true\`) (For installations from source run and paste the output of: \`sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true\`) (we will only investigate if the tests are passing)

Possible fixes

Edited by 🤖 GitLab Bot 🤖