-
Notifications
You must be signed in to change notification settings - Fork 0
mrc-6404 Fix for latest packit #51
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
mrc-6404 Fix for latest packit #51
Conversation
on: | ||
schedule: |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Not sure why this was running on a schedule, doesn't feel like we need it now!
name: packit | ||
tag: mrc-4261 | ||
name: montagu-packit | ||
tag: mrc-5140-trusted-headers |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
how do you want to handle the merge order here? Keep this for now as mrc-ide/packit#187 is in draft?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Yeah, for the moment. Looks like that's what we did before!
Some small fixes to get orderly-web-deploy working with current packit so we can test alongside each other:
montagu-packit
docker image which sets base urls for/packit
and/packit/api
.auth.enabled
to false! I'm assuming that any Packit deployed via OrderlyWeb will be done in non-prod environments at this point, which are not publicly accessible, so it should be ok to disable auth. Montagu authentication will be applied to Packit deployed alongside Montagu on VIMC prod when available (via Montagu deploy).There is one issue I'm not quite sure how to deal with - I was intermittently seeing the orderly server container failing to start up, and tests were consistently failing apparently for this reason. Looking at the container logs, it seemed that this was due to the sqlite database being locked when the container was attempting to back it up. I wondered if this might be because of outpack server also trying to use it... Currently I've "fixed" the test failures by adding a 5s wait into the constellation when it starts up orderly server to give it time to do the backup before starting outpack server.. but perhaps this isn't sufficient for a real server with real data. We could add a "wait-for-db-backup" script to orderly server? Or could maybe do more checks from the constellation?
To test manuallly:
orderly-web start config/packit
Once this is merged I'll push a new version to PyPI and test that out with montagu-orderly-web on uat.