Sonarqube users are facing 404 error while using API call in pipeline
2023-06-20 13:12:16] Request failed with following error: 404 Client Error: for urlhttps://sonarqube.xxxxx.com/api/measures/component?metricKeys=coverage&component=course-copilot-bff-appsync-service&branch=release/release1.0
scanning failures due to the sonar report processing is in pending state. urlhttps://sonarqube.xxxxx.com/api/ce/task?id=AYjUSugHmXLutnU0tjGe
Thanks for the Suggestion , as of now user are not willing to upgrade to Latest version for a couple of months.
Is there any work around which we should follow during the issue happening , Because this is happening for entire sonarqube users.
Most of the projects faced the same issue , the task is in pending for long time which caused this issue.
But all those pending task completed after 14 hours.
Is there any specific reason for task in pending state for long hours.
It sounds like you had a long-running task ahead of everything else, blocking the queue. When that task finished, everything else could be processed (in the order it arrived).
I would probably cancel the current, long-running task instead of the pending ones. It would then be marked failed and the rest of the jobs in the queue should be processed.
I would be interested to know the details of the job that’s taking so long.
And BTW, if you’re still on SonarQube 8.9, you should prioritize your upgrade.
Additionally, you didn’t mention your edition, but in Enterprise Edition($$), you have the ability to configure multiple background task workers. So in this situation, while one worker is taken up handling your very long job, other workers could handle the rest of the queue.
Data reload is taking more hours and we are using community edition so we cant assign more worker node to the instance. Please help us to cancel the long running task.
Screenshot attached for your reference.
Okay, I was wrong. There’s no good way to cancel the current task. You’ll need to shut SonarQube down. That should stop the current background task, but be aware that it will likely put the project in a bad state.
I suggest that while you have SonarQube shut down, you go ahead & do the upgrade so you back bring it back up in a current, supported version.
I don’t know what’s going on with your instance and your incredibly-long analysis report processing. From the log, I have to guess that it’s hung. But there’s nothing more we can do to help you with this while you’re on an EOL version.
