Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). 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 rh-issues@redhat.com 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 "https://issues.redhat.com/browse/SAT-XXXX", 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.
Description of problem:
Customers are expected to do any package install/update on satellite server via satellite-maintain command, in the Satellite upgrade guide we are suggesting customers to use "yum" command to update rubygem-foreman_maintain package, this package is whitelisted in foreman-protector plugin so it is allowed to update via yum.
When we try to update the rubygem-foreman_maintain package using satellite-maintain command it executes satellite-installer command and that causes unexpected service downtime.
Version-Release number of selected component (if applicable):
Satellite 6.x
How reproducible:
Always
Steps to Reproduce:
1. satellite-maintain packages install rubygem-foreman_maintain
which stops satellite services and execute the installer command.
Actual results:
# satellite-maintain packages install rubygem-foreman_maintain
Running preparation steps required to run the next scenarios
================================================================================
Check if tooling for package locking is installed: [OK]
--------------------------------------------------------------------------------
Running install packages in unlocked session
================================================================================
Confirm installer run is allowed:
WARNING: This script runs satellite-installer after the yum execution
to ensure the Satellite is in a consistent state.
As a result some of your services may be restarted.
Do you want to proceed?, [y(yes), q(quit)] y
[OK]
--------------------------------------------------------------------------------
Unlock packages: [OK]
--------------------------------------------------------------------------------
Install packages: Loaded plugins: product-id, search-disabled-repos, subscription-manager
.
.
.
.
Updated:
rubygem-foreman_maintain.noarch 1:0.5.3-1.el7sat
Complete!
[OK]
--------------------------------------------------------------------------------
Running satellite-installer --upgrade --disable-system-checks: Upgrading, to monitor the progress on all related services, please do:
foreman-tail | tee upgrade-$(date +%Y-%m-%d-%H%M).log
Upgrade Step: stop_services...
Running Stop Services
================================================================================
Expected results:
We should allow and promote customers use satellite-maintain to update the rubygem-foreman_maintain package without running any extra installer related steps.
Additional info:
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 (Satellite 6.8 Satellite Maintenance Release), and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHBA-2020:4365
Description of problem: Customers are expected to do any package install/update on satellite server via satellite-maintain command, in the Satellite upgrade guide we are suggesting customers to use "yum" command to update rubygem-foreman_maintain package, this package is whitelisted in foreman-protector plugin so it is allowed to update via yum. When we try to update the rubygem-foreman_maintain package using satellite-maintain command it executes satellite-installer command and that causes unexpected service downtime. Version-Release number of selected component (if applicable): Satellite 6.x How reproducible: Always Steps to Reproduce: 1. satellite-maintain packages install rubygem-foreman_maintain which stops satellite services and execute the installer command. Actual results: # satellite-maintain packages install rubygem-foreman_maintain Running preparation steps required to run the next scenarios ================================================================================ Check if tooling for package locking is installed: [OK] -------------------------------------------------------------------------------- Running install packages in unlocked session ================================================================================ Confirm installer run is allowed: WARNING: This script runs satellite-installer after the yum execution to ensure the Satellite is in a consistent state. As a result some of your services may be restarted. Do you want to proceed?, [y(yes), q(quit)] y [OK] -------------------------------------------------------------------------------- Unlock packages: [OK] -------------------------------------------------------------------------------- Install packages: Loaded plugins: product-id, search-disabled-repos, subscription-manager . . . . Updated: rubygem-foreman_maintain.noarch 1:0.5.3-1.el7sat Complete! [OK] -------------------------------------------------------------------------------- Running satellite-installer --upgrade --disable-system-checks: Upgrading, to monitor the progress on all related services, please do: foreman-tail | tee upgrade-$(date +%Y-%m-%d-%H%M).log Upgrade Step: stop_services... Running Stop Services ================================================================================ Expected results: We should allow and promote customers use satellite-maintain to update the rubygem-foreman_maintain package without running any extra installer related steps. Additional info: