When I try to add project in my Sonar cloud organization manually I receive error: “An unexpected error occurred. Please try again later“
Also, when I try adding a project thru Azure Devops integration with importing a repo I see error message: “Could not provision some of the projects (0/1)”
There are 2 guys with admin permissions and all of them experience the same. What could be the reason?
Hi,
Welcome to the community and thanks for this report!
Could you provide your organization ID?
Thx,
Ann
My organization name is Pandora Jewelry with a key pandora-jewelry
Hi,
Thanks! I’ve flagged this for the team.
Ann
Can you give me the organization key? I will send you a PM to share this information.
Hi @dragan can you please share when (date and time, or at least date) you did the failed calls?
sorry for the late answer
I have just tried and still receiving the same error messages as I described in my first post.
Do you have any update on this?
We have the same problem. Using the WebUI, the “provision” step returns a 400 status with the already reported error message.
Using the API (https://sonarcloud.io/api/projects/create), the response is 500.
Hi @Fabian.Kreutz,
Welcome to the community and thanks for this report!
Can you provide your organization key?
Thx,
Ann
Thank you.
All information is in the screenshot (date and also organization). We have several organizations, but one is agco-onedigital.
Is there an channel for enterprise support?
Hi @Fabian.Kreutz,
Thanks.
Commercial support is available if you’d like to go that route. You can ping your sales contact to follow up if you like.
In the meantime, this thread is flagged for the experts, and I expect them to show up soon.
Ann
Thanks. I asked the people who have contact to the sales contacts to contact them.
In the meantime I found that I am able to analyse another project newly, but for this particular one, it still fails. So it seems to be repository- or name- related and not account/organization/user-related.
Hi,
Thanks for the details. This is flagged for the team. Hopefully they’ll be along soon.
Ann
Hi again,
Do you have spaces or dashes in your project name?
Thx,
Ann
Lots of dashes in all our repository names. No spaces.
I just checked particularly the one that is not working and there are no funny non-ascii characters in it either.
Hi,
Thanks for checking.
Ann
Hey, some more information.
We tried this: Renamed the github repository, then provisioned a sonar project on the new name (which worked!), renamed the github repository back to the name that originally did not work and updated the key in the sonar project.
So now the issue is solved for us.
Hi,
I’m glad you worked through this. Still, I think you shouldn’t have had to, so I’m going to leave this in the team’s queue. They may come back with questions for you. Hopefully that will be okay.
Thx,
Ann
Hi,
@Fabian.Kreutz Can you share how you renamed the GitHub repository to have it correctly imported in SonarQube Cloud? Did you remove the hyphens? Did you do something else?
@dragan Can you share the key/name of one repository that is failing to be imported into SonarQube, please? I’d like to check if there could be anything in these fields that SonarQube doesn’t interpret correctly.
Thank you
We found out that Sonar does not let us create a project with a project key containing a string that is used for defining permission template. So we now create project manually and then update project key value to align with our naming convention and apply permission template manually (instead of being applied automatically as before). I am attaching a screenshot of our permission template that is matching string ”dol” in project key and applying permissions accordingly.
