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.
DescriptionVedashree Deshpande
2021-04-23 15:40:25 UTC
Description of problem:
Explained with Example by the Customer
We have 1 Satellite, 3 Capsules, 1800 hosts and 20 organisations.
20 organisations = at least 20 different sysadmin teams.
We (our central team) control (more or less) the Satellite & Capsule systems, so we can upgrade them approximately at the same time.
But as listed in the official docs, the tools NEED to be at the same version as the central Satellite.
So upgrade of the tools need to be done on ALL systems, by ALL the system admins.
Ensuring upgrade is done by 20 different teams, successfully on 1800 hosts is a complicated tasks, especially if it needs to be done "right at the time" of the satellite upgrade.
I'm not asking much, just an official support of the N-1 satellite by the tools.
This way, we would be able to update the tools 1 month before the update of the satellite, and be ready when we upgrade the satellite.
We will be solving this in Satellite 7.0 and later with the removal of 'versioned' Satellite Tools repositories for each release of Satellite.
We will only have 1 repository for Satellite 7 Tools, eg:
rhel-7-server-satellite-tools-7-rpms
satellite-tools-7-for-rhel-8-x86_64-rpms
these repositories will be supported across all versions of Satellite 7 and not require immediate upgrades to your clients at time of upgrade of the Satellite.
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 (Important: Satellite 6.12 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/RHSA-2022:8506
Comment 11Red Hat Bugzilla
2023-09-18 00:25:59 UTC
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days