Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira ( If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1765519 - "foreman-maintain packages install" redundantly upgrades Satellite
Summary: "foreman-maintain packages install" redundantly upgrades Satellite
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Satellite Maintain
Version: 6.6.0
Hardware: x86_64
OS: Linux
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Jameer Pathan
Depends On:
TreeView+ depends on / blocked
Reported: 2019-10-25 10:30 UTC by Pavel Moravec
Modified: 2023-04-28 14:04 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Last Closed: 2021-10-28 14:36:13 UTC
Target Upstream Version:

Attachments (Terms of Use)

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:

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

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,


Comment 8 Francesco Ratto 2020-08-05 07:36:27 UTC
Again requesting for updates on this 


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,


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:

Note You need to log in before you can comment on or make changes to this bug.