-
Notifications
You must be signed in to change notification settings - Fork 196
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
Cleanup the setup from the database related bits #9827
base: master
Are you sure you want to change the base?
Conversation
👋 Hello! Thanks for contributing to our project. You can see the progress at the end of this page and at https://github.com/uyuni-project/uyuni/pull/9827/checks If you are unsure the failing tests are related to your code, you can check the "reference jobs". These are jobs that run on a scheduled time with code from master. If they fail for the same reason as your build, it means the tests or the infrastructure are broken. If they do not fail, but yours do, it means it is related to your code. Reference tests: KNOWN ISSUES Sometimes the build can fail when pulling new jar files from download.opensuse.org . This is a known limitation. Given this happens rarely, when it does, all you need to do is rerun the test. Sorry for the inconvenience. For more tips on troubleshooting, see the troubleshooting guide. Happy hacking! |
03556e9
to
8c5ee87
Compare
1844f82
to
4704df8
Compare
This PR needs the changes in https://build.opensuse.org/package/show/home:cbosdonnat:branches:systemsmanagement:Uyuni:Master:Docker/uyuni-master-pgsql in order for the Java unit tests to pass. Getting the image submitted before the PR would break all other tests based on master with |
cf6f990
to
4e8560b
Compare
095b365
to
e8bb270
Compare
5ee9069
to
f4d39a1
Compare
PostgreSQL containers rely on the postgresql process to be PID1 and receiving SIGINT. Without exec the entrypoint shell is still the PID1 and would not pass the signal to the child.
c186bc9
to
21d0087
Compare
The DB setup is now either handled in the DB container init for what requires superuser permissions or in `mgr-setup`. All other DB setup bits from spacewalk-setup and uyuni-setup-reportdb can now be removed. Writing the DB properties to rhn.conf still has to happen in `spacewalk-setup` due to the way that file is generated by satcon script. This would be a mess to cleanup in a future PR. The DB users are no longer superusers, so uyuni-setup-reportdb-user has to handle the user deletion a bit differently as only the user itself or a superuser can drop the objects it owns.
21d0087
to
d5815a6
Compare
d5815a6
to
18a8e43
Compare
What does this PR change?
Moving the database to a separate container requires to cleanup several things:
GUI diff
No difference.
Documentation
Documentation issue was created: Link for SUSE Manager contributors, Link for community contributors.
(OPTIONAL) Documentation PR
DONE
Test coverage
Cucumber tests were adjusted
DONE
Links
Issue(s): Part of https://github.com/SUSE/spacewalk/issues/25363
Changelogs
Make sure the changelogs entries you are adding are compliant with https://github.com/uyuni-project/uyuni/wiki/Contributing#changelogs and https://github.com/uyuni-project/uyuni/wiki/Contributing#uyuni-projectuyuni-repository
If you don't need a changelog check, please mark this checkbox:
If you uncheck the checkbox after the PR is created, you will need to re-run
changelog_test
(see below)Re-run a test
If you need to re-run a test, please mark the related checkbox, it will be unchecked automatically once it has re-run:
Before you merge
Check How to branch and merge properly!