Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 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 "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". 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 "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-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.
Unable to perform upgrade without access to CDN or subscription-manager, there is the need to use custom repositories and skip subscription-manager this is currently not supported nor well documented.
This is expected behaviour. Currently, documentation is clear about that - from the section 1.1 Requirements:
- The system registered to the Red Hat Content Delivery Network or Red Hat Satellite 6.5 or later using the Red Hat Subscription Manager
There is not currently any supported way of in-place upgrades on disconnected systems.
Hi,
This is Edward Jin, Platform TAM based in Beijing.
This feature should be vital for customers to consider RHEL 8 in-place upgrading.
Because most of our FSI customers in CN are running RHEL on disconnected environment and no Satellite servers.
And, we have already introduce in-place upgrading to customers, and they see this method as an option.
If we would like to let customers choose in-place upgrading, I think that Leapp upgrade for offline systems should be implemented and supported.
Thanks.
Best Regards
Edward
To be clear, we are going to provide solution to upgrade without RHSM, so customers will be able to deliver own repositories on their own responsibility. The documentation will be published after the release.
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-2020:1959