Unable to Remove User from SonarCloud Organization

SonarQube Cloud
, ,
1

Hi Team,

I’m facing an issue with removing a user from my SonarCloud organization, and I’ve tried multiple approaches without success. Here’s a summary of what’s happening:

  1. GitHub Sync Not Working
  • The user was removed from our GitHub organization, but they are still listed in SonarCloud despite GitHub sync being enabled.
  • I expected the sync to automatically remove them, but it hasn’t worked.
  1. Tried Disabling Sync & Manual Removal
  • I disabled the GitHub sync, hoping I could manually remove the user.
  • The “Remove from Organization” option appeared, but clicking it results in a 500 Internal Server Error.
  1. Group Membership Issues
  • I successfully removed the user from all custom groups, except the default “Members” group.
  • SonarCloud does not seem to allow modifications to this group.
  1. Tried Using the API
  • I attempted to remove the user via the SonarCloud API, but received the following error:
Error 400: Default group 'Members' cannot be used to perform this action
  • This makes it impossible to remove the user via API as well.

Seeking Guidance

At this point, I am out of options. I am an administrator in the organization, but I still cannot remove the user.

Is there a workaround for this issue? Any guidance on how to resolve this would be greatly appreciated.

Thank you!

2

I’ve sent you a private message to collect some additional info

3

Hey again!

So I had a look, and it looks like the API POST api/organizations/remove_member started throwing 500 errors around 5pm yesterday (CET). The endpoint had not returned any errors like this in the 3 weeks prior, so I’ve raised an incident internally. I’ll keep this thread updated.

1 Like
4

We’ve identified the problem and we’re working on a fix. Thanks for your patience.

5

User cannot be removed from the organization. The error comes like unexpected. Please try again later.

6

Hey @Manika

See above!

7

Hey @aperuru and @Manika

The issue should now be resolved. Can you try again?

8

@Colin Issue resolved, thank you for the quick fix.