When we merged https://github.com/ansible/galaxy_ng/commit/5776b89259352b871c8686d5e0f54facba7ad393 with pulp-ansible==0.16.0 an automatic backend stage deploy started but did not complete.

Initial investigation saw some content-app and pulp-worker pods not ready, the logs showed they were waiting for migrations. A short while later the api logs were checked and it showed migrations applied… but this seems to be the result of a 2nd automatic backend stage deploy triggered by https://github.com/ansible/galaxy_ng/commit/a4a1bf38b0055cc51a9b15f6d82e19d96199ef99. At this point the migrations applied successfully and the app worked as expected.

Just want to get infrastructure eyes on this before this prod CRC deploy.