Project

General

Profile

Actions
Copy link

Bug #31763

closed

satellite-clone restores postgresql.conf with root:root ownership causing failure to clone

Added by Mike McCune almost 4 years ago. Updated almost 4 years ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
Tooling
Target version:
-
Difficulty:
Triaged:
Yes
Bugzilla link:
1922503
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

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.

Actions
Copy link

Also available in: Atom PDF