[DO NOT MERGE] ci-autofix: Investigate red master CI

[hashicorp-vault-sonar-prod]

---

Summary by Gitar

• CI Fixes:
  • Investigate and resolve failing CI run 111682659586

_{This will update automatically on new commits.}

[hashicorp-vault-sonar-prod]

gitar master CI is failing: https://github.com/SonarSource/sonar-xml/actions/runs/37280217590/job/111682659586

1. Investigate the failure.
2. If it looks transient or flaky, retry it.
3. If it's a real issue, fix it in this PR.
4. After pushing a fix, recheck the PR's CI status, and keep pushing commits until it passes.
5. If you can't fix it, leave a comment explaining your investigation.
6. If there's nothing to fix, leave a comment with your investigation notes, ending it with exactly "let's close this PR".

[gitar-bot]

Investigation notes

Pulled the full logs for job 111682659586.

• The Maven build compiled successfully and all 225 unit tests passed (Tests run: 225, Failures: 0, Errors: 0, Skipped: 0).
• The actual failure happened later, during the SonarQube scanner bootstrap step:

  [ERROR] Failed to query server version: Call to URL [***/api/v2/analysis/version] failed: HTTP connect timed out
  [ERROR] Failed to execute goal org.sonarsource.scanner.maven:sonar-maven-plugin:5.6.0.6792:sonar (default-cli) on project xml: The scanner bootstrapping has failed!
  

• There's also an unrelated warning earlier in the log that the Develocity remote build cache was disabled due to errors (Build cache at 'https://develocity-public.sonar.build' is not a Develocity build cache that is compatible with Maven builds.), which is also infrastructure-side.

Both issues are network/connectivity failures reaching internal SonarQube/Develocity infrastructure from the runner, not a code or test defect in this repository. There is no code change to make here.

let's close this PR

[datadog-sonarsource]

❌ Errors

Your PR has failed checks. Please review the issues below and take necessary action before merging.

🚦 1 Pipeline job failed

Build | Build

View more details · View in GitHub Actions

Useful? React with 👍 / 👎

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: 9945523 | Docs | View more details | Give us feedback!}

[gitar-bot]

CI failed: Maven build failed during the SonarQube analysis step due to an infrastructure-level HTTP 503 Service Unavailable error from the Sonar server.

Overview

1 log analyzed showing a failure during the SonarQube analysis step due to a server availability issue (HTTP 503 Service Unavailable).

Failures

SonarQube Scanner Bootstrapping Failure (confidence: high)

• Type: infrastructure
• Affected jobs: 111738696000
• Related to change: no
• Root cause: The SonarQube server returned an HTTP 503 Service Unavailable error when queried during the sonar:sonar goal execution, causing the scanner bootstrapping to fail.
• Suggested fix: Rerun the CI job once the SonarQube server is healthy and operational.

Summary

• Change-related failures: 0
• Infrastructure/flaky failures: 1 (SonarQube server HTTP 503 error)
• Recommended action: Rerun the CI job since the failure is caused by an external service unavailability.

Options ✅ Auto-apply

✅ Auto-apply is on → Gitar will commit updates to this branch.
Display: compact → Counting what did not apply, without listing it.

Comment with these commands to change the behavior for this request:

✅ Auto-apply	Compact
gitar auto-apply:off	gitar display:verbose

_{Was this helpful? React with 👍 / 👎 | Gitar}