Description of problem:
User scenario: on a freshly installed Sat6.6, fully updated system, I want to install PCP, so I run:
foreman-maintain packages install pcp-zeroconf
This triggers after package install:
1) execution of satellite-installer (redundant, but let say still ok),
2) it runs it with --upgrade option, that stops all services and attempts to upgrade fully upgraded Satellite.
That seems as an overkill. Why installing a monitoring SW requires 10m+ downtime of all services and running steps like e.g. katello:clean_backend_objects?
Version-Release number of selected component (if applicable):
Sat 6.6 GA
Steps to Reproduce:
1. Install Sat6.6 on fully updated RHEL7.7
2. foreman-maintain packages install pcp-zeroconf
3. Confirm everything
the install command triggers also "satellite-installer --upgrade --disable-system-checks" sub-command, despite there was no reason for it
Ideally, foreman-maintain should identify if satellite-installer must be run at all (I can imagine we install/update something that alters some config that is maintained by installer - so then satellite-installer should reset it). And run it only when something needs to be reset that way.
Or at least foreman-maintain should trigger installer upgrade _only_ when f-m upgraded some Satellite-related process.
IMHO it would make sense to make the "satellite-installer" run to be disabled - assuming the operator knows what he is doing.
Taking down Satellite for minutes just because some non-Satellite related package got installed seems a bit of an overkill to me. And this is not what that said operator would expect from his activity.
While some packages would interfere with Satellite and the installer will have to be run afterwards, it should not be mandatory for every package you install afterwards.