TL;DR If you’ve landed on this thread because you’re analyzing on SonarCloud and getting the error message in the title, please wait 10 minutes and try again.
Hi all,
We just finished our postmortem on this & for a couple reasons I want to follow up here with what we found:
The problem was caused by a combination of factors:
- Blue/Green deployment
- the addition of a rule parameter in an update to CSS analysis
From the relevant (internal) ticket:
The new rule parameter is added to the [database] during the startup of the web leader in the inactive group.
After the rule parameter was inserted into the DB it is included in the
api/rules/searchendpoint. This endpoint is used by our scanners to load all the rules in the project’s QP.However, the latest version of the analyzers does not get served until the blue/green deployment is fully completed. So during the duration of the blue/green deployment, the analyzer is initialised with a rule parameter that it does not know, which can lead to failures like [what we saw here]
I.e., this error was essentially transient for the ~10min Blue/Green deployment takes
And when we re-deploy this CSS update sometime in May, we’ll face it again. To mitigate the impact, we’ll make sure deployment happens during a low-activity time of day.
But if you’re analyzing on SonarCloud in May 2022 and seeing this error, please wait 10 minutes and try again. If you still get the error, then please do open a new thread.
Ann