How to use the noop option to check for changes in Satellite config files when running satellite-installer

Solution Verified - Updated 14 Jun 2024

Environment

Red Hat Satellite 6.

Issue

The Satellite 6 installer script is based on Puppet, which means that any manual configuration changes will be overwritten to the installation defaults. You can use the --noop argument when you run the installer script to determine what changes would be applied when you run it. This argument ensures that no actual changes are made.
Hiera users, in particular, can use this method to check in advance what changes will be made by running the installer script.

Resolution

If you have custom Puppet configurations, they will be reverted to the installation defaults when you run the installer script. If you want to see what will be changed run the installer, you can enter the installer command with the --noop (no operation) option and review the changes that will be applied when you run the installer script without the noop argument.

Add the following line to the /etc/httpd/conf/httpd.conf configuration file.
```
Include /etc/httpd/conf.modules.d/*.conf
```
Restart the httpd service.
- On Red Hat Enterprise Linux 6, enter the following command:
```
# service httpd restart
```
- On Red Hat Enterprise Linux 7, enter the following command:
```
# systemctl restart httpd
```
Restart the databases.

On a Satellite, start the postgresql and mongod database services.
- On Red Hat Enterprise Linux 6, enter the following command:
```
# service postgresql start
# service mongod start
```
- On Red Hat Enterprise Linux 7, enter the following command:
```
# systemctl start postgresql
# systemctl start mongod
```
On a Capsule, start the mongod database service.
- On Red Hat Enterprise Linux 6, enter the following command:
```
# service mongod start
```
- On Red Hat Enterprise Linux 7, enter the following command:
```
# systemctl start mongod
```
Enter the command with the --noop option as follows.
```
# satellite-installer --scenario satellite --verbose --noop
```
Review the /var/log/foreman-installer/satellite.log or /var/log/foreman-installer/capsule.log. to see what changes would be applied if the --noop option was omitted. Look for the \+++ and --- symbols indicating changes to configurations files. Because the above "no operation" command does not actually create the files, and some Puppet resources in the module expect them to be there, some failure messages are to be expected.

This solution is part of Red Hat’s fast-track publication program, providing a huge library of solutions that Red Hat engineers have created while supporting our customers. To give you the knowledge you need the instant it becomes available, these articles may be presented in a raw and unedited form.