Bug #31763
closed
satellite-clone restores postgresql.conf with root:root ownership causing failure to clone
Description
When cloning a 6.7 Satellite server, we perform the following steps:
1) install postgresql server packages:
2) untar config files:
3) remove postgresql.conf
4) run satellite-installer:
The issue is that satellite-installer does not properly re-set file permissions on postgresql.conf to postgresql:postgresql upon execution of the Puppet code to configure this file, it ends up being root:root as it likely doesn't expect this file to be completely missing.
This causes postgreql server to fail to start and the clone to fail completely.
We need to investigate removing the step (3) above and see if we still need to continue removing this config file as test runs without this step complete properly.
Updated by James Jeffers about 3 years ago
- Status changed from New to Closed
Closing as we will work off the BZ and work the issue in the proper trackers there.
Updated by John Mitsch about 3 years ago
It could be an installer fix, but I think we need a bit more investigation to figure out where the upstream changes should live (sat-clone, foreman-maintain, and/or installer) and file more specific bugs. We can work off the BZ for now and take it from there. @mike geller let me know if you want to approach it differently or had something else in mind!