Closed jharmison-redhat closed 4 years ago
Confirmed to be a timing issue. SonarQube starts answering requests at the route before the service comes all the way up, so the wait for that period should wait for "SonarQube is up" in the pod logs rather than waiting for responses at the route.
SonarQube deployment failures appear sporadically. It's potentially just a timing issue. Rerunning the playbook right now results in a clean application of the role, including user creation.