Force_boot rabbit if mnesia exists

[grahamneville]

SUMMARY

related #5314

tells rabbit to force_boot if mnesia database already exists

ISSUE TYPE

• Bugfix Pull Request

COMPONENT NAME

• Installer

AWX VERSION

ADDITIONAL INFORMATION

helm/charts#13485

[softwarefactory-project-zuul]

Build failed.

• awx-api-lint : SUCCESS in 2m 55s
• awx-api : FAILURE in 2m 45s
• awx-ui : FAILURE in 2m 45s
• awx-ui-next : FAILURE in 2m 39s
• awx-swagger : FAILURE in 2m 41s
• awx-detect-schema-change : FAILURE in 2m 22s (non-voting)
• awx-ansible-modules : FAILURE in 2m 39s

[shanemcd]

I don't love the idea of adding more inline scripts here. Is there a reason not to add it to the startup script in the container? I see you linked to it in the referenced issue.

[grahamneville]

Adding it directly in to launch.sh on the container (by editing the Dockerfile) isn't possible as we won't know the exact directory name created inside /var/lib/rabbitmq/mnesia/ for that pod. This is why we use the ${RABBITMQ_NODENAME} kubernetes var.

Another way to do this is to add it as a configmap and mount it as a volume over the top of launch.sh.
If that's preferred I'll alter the PR.

P.S. https://github.com/ansible/awx-rabbitmq doesn't look to contain the latest code for 3.7.15.

[shanemcd]

This is why we use the ${RABBITMQ_NODENAME} kubernetes var.

It is available inside of the container as an environment variable. This could be solved with a conditional in the launch script that detects when it is set.

Another problem with this approach is that our downstream images are not based on Alpine.

P.S. https://github.com/ansible/awx-rabbitmq doesn't look to contain the latest code for 3.7.15.

It is the same code, but I ran RABBITMQ_VERSION=3.7.15 make docker-build. I will update the default variable in the Makefile. Thanks for bringing that to my attention.

[grahamneville]

Closing, replaced with #5317