Description of problem:
"satellite-installer --scenario satellite" may use stale pgsql data and import the data during a new installation
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Install a new RHEL host with mounted filesystems following guidelines :
2. Install Satellite server bits
# yum install satellite
3. Remove  Satellite 6.3 server bits:
4. Change hostname to something else
# hostnamectl set-hostname satname2
5. Install Satellite server bits again
# yum install satellite
Satellite installer uses the stale data from /var/lib/pgsql and this results in two default/local capsules being created.
Install tells the user that it completes successfully, unaware of the creation of the two default/local capsules.
Satellite installer should detect the old /var/lib/pgsql data during a new initial installation and warn the user about the data still existing.
Option to completely remove the data during the Satellite installer process.
It looks like this bug is a side affect of bug 1574257; therefore, should we close this one?
(In reply to Brad Buckingham from comment #1)
> Hi Sam,
> It looks like this bug is a side affect of bug 1574257; therefore, should we
> close this one?
It is because of it, but we should still IMHO have the installer check to make sure the filesystem is completely empty before installing the bits.
Just kind of scary that it can still import that information somehow when running a fresh installation.
You are far from running a fresh installation if you have installed Satellite, and then performed a katello-remove.
This is not a full-service item (today) to let you cleanly start over with Satellite.
If you had previously installed Satellite, you should be using the --reset option on the next installer run which will include dropping the databases before performing installation.
This has always been the case, and often it is recommended simply to reinstall RHEL after /attempting/ an installation - because katello-remove is quite far from covering all facets of items that are added or configuring during an installation.
Thanks I understand what you're saying. But per the customers view, and I do tend to agree with them, they shouldn't have to reinstall everything every time something goes awry with Satellite.
We see this quite often, "oh it's broke, just reinstall from a clean start".
Customers prefer not to reinstall because of the amount of work it took them to build the physical server from the ground up.
In this situation, the customer and I relied on katello-remove to do its job and "remove" the data directories cleanly. Of course, it did not and we spent a few days trying to figure out the capsule id issue and also why this occurred.
It would've been nice that the *if* the installer would've said "Hey, there's data here, should we remove this data before proceeding?" versus a few days of trying to find out why stuff didn't work and that the installer say that everything installed correctly, delaying yet another migration and causing the customer to lose additional confidence in this product.
Verified on 6.7 Snap10, katello-remove command removed.
# rpm -q katello-3.14.0-5.el7sat.noarch
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.