Bug 1765519

Summary:	"foreman-maintain packages install" redundantly upgrades Satellite
Product:	Red Hat Satellite	Reporter:	Pavel Moravec <pmoravec>
Component:	Satellite Maintain	Assignee:	satellite6-bugs <satellite6-bugs>
Status:	CLOSED CURRENTRELEASE	QA Contact:	Jameer Pathan <jpathan>
Severity:	high	Docs Contact:
Priority:	high
Version:	6.6.0	CC:	ableisch, apatel, ehelms, fperalta, fratto, inecas, jpathan, kgaikwad, mbacovsk, mschibli, mvanderw, rmynar
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	x86_64
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2021-10-28 14:36:13 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Pavel Moravec 2019-10-25 10:30:44 UTC

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


How reproducible:
100%


Steps to Reproduce:
1. Install Sat6.6 on fully updated RHEL7.7
2. foreman-maintain packages install pcp-zeroconf
3. Confirm everything


Actual results:
the install command triggers also "satellite-installer --upgrade --disable-system-checks" sub-command, despite there was no reason for it


Expected results:
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.


Additional info:

Comment 4 Andreas Bleischwitz 2020-01-16 08:35:53 UTC

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.

Comment 7 Francesco Ratto 2020-07-22 14:54:35 UTC

Hi,

may we get an update on the status of this BZ? Our customers are asking whether we still take care of their requests.

Thanks a lot,

  Francesco

Comment 8 Francesco Ratto 2020-08-05 07:36:27 UTC

Again requesting for updates on this 

Hi,

may we get an update on the status of this BZ? Our customers are asking whether we still take care of their requests.

Thanks a lot,

  Francesco

Comment 11 Francesco Ratto 2020-09-22 22:32:52 UTC

Can you pls give us infos about ?

Comment 12 Anurag Patel 2020-10-03 21:11:15 UTC

The foreman-protector plug-in is shipped to ensure stability of Satellite system. However if this behaviour is not desired, package version locking can be disabled in Satellite. For more context, please read the statement here: https://bugzilla.redhat.com/show_bug.cgi?id=1754883#c13