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.
Created attachment 1266754[details]
hotfix
Satellite hotfix tool
---------------------
Usage (tarball extraction):
tar -xzf satellite-hotfix-1436242.tar.gz
cd satellite-hotfix
Usage (dry run):
./satellite-hotfix -n 1436242
Usage:
./satellite-hotfix 1436242
Revert a hotfix:
./satellite-hotfix -r 1436242
List all available hotfixes:
./satellite-hotfix
The numbers are real Red Hat Bugzilla numbers. All backup and reject files are
save in backups/ sub-directory. Please keep the tarball for possible reverting
of the change in the future. If patching fails, revert immediately and report
the output. After each Satellite update, this hotfix process must be repeated
if the updated does not include the bugfix yet, search in errata notes for
bugzilla numbers to confirm. Hotfixes are distributed in tarballs with date
timestamps, new tarball obsoletes the old one and includes all previous
patches.
If system-wide Ruby is not installed for some reason, use Satellite Foreman
Ruby software collection:
scl enable rh-ruby22 -- ./satellite-hotfix -h
To find out Ruby versions available do:
ls /opt/*/*ruby* -d
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.
https://access.redhat.com/errata/RHBA-2017:1553
Created attachment 1266754 [details] hotfix Satellite hotfix tool --------------------- Usage (tarball extraction): tar -xzf satellite-hotfix-1436242.tar.gz cd satellite-hotfix Usage (dry run): ./satellite-hotfix -n 1436242 Usage: ./satellite-hotfix 1436242 Revert a hotfix: ./satellite-hotfix -r 1436242 List all available hotfixes: ./satellite-hotfix The numbers are real Red Hat Bugzilla numbers. All backup and reject files are save in backups/ sub-directory. Please keep the tarball for possible reverting of the change in the future. If patching fails, revert immediately and report the output. After each Satellite update, this hotfix process must be repeated if the updated does not include the bugfix yet, search in errata notes for bugzilla numbers to confirm. Hotfixes are distributed in tarballs with date timestamps, new tarball obsoletes the old one and includes all previous patches. If system-wide Ruby is not installed for some reason, use Satellite Foreman Ruby software collection: scl enable rh-ruby22 -- ./satellite-hotfix -h To find out Ruby versions available do: ls /opt/*/*ruby* -d