Last Analysis Failed: ed14d11b-cc72-47f2-95a8-5e51c4e88b6b

SonarQube Cloud
1

Analysis failures on one of our projects, and not seeing new pull requests (analysis hangs, but don’t see any information in background tasks/etc)

  • CI system - GitHub Actions
  • Analysis Method - Automatic Analysis Enabled
  • Error Analysis Failure 
    • Analysis status
The last analysis has failed. If it keeps on failing after several attempts, please contact us on Community forum (opens in new tab) and provide the following failing analysis ID: ed14d11b-cc72-47f2-95a8-5e51c4e88b6b.
  • Error new pull requests not seen in sonar UI, gh action hangs: 
    • SonarCloud Code AnalysisExpected — Waiting for status to be reported
  • Analysis ID failures
    • ed14d11b-cc72-47f2-95a8-5e51c4e88b6b
    • 5793a972-66f4-4f86-9f82-690741a644a1
  • Steps to reproduce
    • Toggled automatic analysis off/on to trigger new scan, analysis fails every time (with new analysis id)
Sonar Community Roundup; Feb 14 - 20
2

Hi,

Welcome to the community and thanks for this report!

Analysis errored-out because it hit a YAML file it couldn’t handle. Unfortunately I don’t have the name of the file, but you could set an exclusion for *.yaml (or whichever suffix you use) and that should work.

 
HTH,
Ann

4

Odd, we didn’t add any new yaml files since it started failing, nor did adding an exclusion for yaml files that did change since failure have any effect.

Do you have the error it returned so we can narrow down and not do a blanket yaml exclusion policy?

Excluding all yamls did get scan to succeed.

1 Like
5

Hi,

This is all I’ve got

org.sonar.iac.common.extension.ParseException: Unexpected empty nodes list while converting file

I had already flagged this thread for the folks who own IaC analysis because they’ll be interested that there was a parsing error.

Knowing that it’s a change in behavior, makes it even more interesting. I’ll make sure this doesn’t fall through the cracks.

 
Ann

1 Like
6

Hi again,

Actually, I can tell you that it comes from a Kubernetes Kustomization file.

 
HTH,
Ann

7

Yeah – I had just figured it out, believe that’s a change in behavior since we’ve had some of these files around for months. Context: We have some yaml files that act as placeholders, they don’t contain {}, completely empty files so no bytes of data.

Our scans are working again though, thanks for the assistance.

2 Likes
8

Hi,

That’s very helpful! Thanks!

 
Ann

9

Hello @carrxion,

thanks for reporting the issue, it helped us to quickly resolve a bug in a new feature we implemented.

To follow up on this:

Ann was right, the issue was because of a parsing error in an empty kustomization.yaml file.

We fixed the issue and released a new version of the responsible analyzer on 12th Feb.

How did you resolve the issue on your side?
If you excluded the file, you should be able to revert this change.

Best
Jonas

1 Like
13

@jonas.wielage We added **/kustomization.yaml to Source File Exclusions

Confirmed that removing exclusion & rerunning scan succeeds now.

Thanks!

2 Likes
14

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.