When cloning a 6.7 Satellite server, we perform the following steps: 1) install postgresql server packages: https://github.com/RedHatSatellite/satellite-clone/blob/81e3be94c5f34887dfe133e9309946a1bd31c175/roles/satellite-clone/tasks/main.yml#L123 2) untar config files: https://github.com/RedHatSatellite/satellite-clone/blob/81e3be94c5f34887dfe133e9309946a1bd31c175/roles/satellite-clone/tasks/main.yml#L194 3) remove postgresql.conf https://github.com/RedHatSatellite/satellite-clone/blob/81e3be94c5f34887dfe133e9309946a1bd31c175/roles/satellite-clone/tasks/main.yml#L198 4) run satellite-installer: https://github.com/RedHatSatellite/satellite-clone/blob/81e3be94c5f34887dfe133e9309946a1bd31c175/roles/satellite-clone/tasks/main.yml#L235 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.
This shouldn't be a problem since Foreman 2.4 (so Satellite 6.10+) as that has an updated puppet-postgresql module which contains [1]. This also explains why I was never able to reproduce the error in my tests. Would you consider this done then? [1] https://github.com/puppetlabs/puppetlabs-postgresql/commit/171a1be93df8113fce82460d3c9b07f17974af4f
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 500 days