-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
Affects Version/s: 7.6.6, 7.6.7, 7.10.0, 7.10.1, 7.10.2, 7.11.0, 7.11.1
-
Component/s: Data Center - Other
-
7.06
-
Severity 2 - Major
Symptom
The /status endpoint returns a 503 error instead of FIRST_RUN on initial install. This means that any load balancer which relies on /status to report will not see the node as running. In AWS Cloudformation, this means that any new stack on versions 7.6.6, 7.6.7, 7.10.x, 7.11.0, and 7.11.1 will not work - the nodes are up and running but they are never added into the load balancer pool.
Workaround
- Access the node directly (in AWS you will need to add your IP to the security group on the port that Jira is running on)
- Run through the setup wizard
- Once setup is complete, the /status endpoint will return RUNNING and the nodes will be added to the load balancer