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.
Bug 1750737 - [RFE] Leapp upgrade for offline systems
Summary: [RFE] Leapp upgrade for offline systems
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: leapp-repository
Version: 7.6
Hardware: x86_64
OS: Linux
unspecified
medium
Target Milestone: rc
: ---
Assignee: Petr Stodulka
QA Contact: Alois Mahdal
URL:
Whiteboard:
: 1662307 (view as bug list)
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2019-09-10 11:49 UTC by Kenny Tordeurs
Modified: 2023-09-07 20:34 UTC (History)
9 users (show)

Fixed In Version: leapp-repository-0.10.0-2.el7_8
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2020-04-29 01:45:58 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2020:1959 0 None None None 2020-04-29 01:46:15 UTC

Description Kenny Tordeurs 2019-09-10 11:49:05 UTC 
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.
Comment 6 Petr Stodulka 2019-09-11 15:19:10 UTC 
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.
Comment 7 Michal Bocek 2019-09-11 16:53:58 UTC 
Petr, Kenny knows it is not supported at the moment. He writes that in the description, and that's also why he marked it as RFE.
Comment 9 xujin 2019-11-19 09:54:04 UTC 
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
Comment 15 Michal Bocek 2020-04-16 15:13:56 UTC 
*** Bug 1662307 has been marked as a duplicate of this bug. ***
Comment 21 Petr Stodulka 2020-04-27 12:34:46 UTC 
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.
Comment 23 errata-xmlrpc 2020-04-29 01:45:58 UTC 
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
Note You need to log in before you can comment on or make changes to this bug.