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 1526619 - support rhel 6.10 in-place upgrades to rhel 7.4 for SAP HANA installations
Summary: support rhel 6.10 in-place upgrades to rhel 7.4 for SAP HANA installations
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: preupgrade-assistant-el6toel7-sap
Version: 6.7
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: rc
: ---
Assignee: Petr Stodulka
QA Contact: Daniel Yeisley
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-12-15 21:06 UTC by Terry Bowling
Modified: 2022-03-13 14:35 UTC (History)
11 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2019-01-16 09:14:44 UTC
Target Upstream Version:
Embargoed:
aarnold: needinfo-

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHEA-2019:0070 0 None None None 2019-01-16 09:14:46 UTC

Description Terry Bowling 2017-12-15 21:06:33 UTC 
Because SAP HANA is only certified for specific RHEL minor releases, it is important to support in-place upgrades to those certified minor releases.

Today, the target is:
     RHEL 6.7 -> RHEL 7.3

This might change in the future, but this is the current requirement.
Comment 2 Petr Stodulka 2018-06-13 10:36:26 UTC 
Just update info, that nowadays we are talking about upgrade to RHEL 7.4 with required update to RHEL 6.10 as an interim step.
Comment 7 Arne Arnold 2018-11-04 20:13:06 UTC 
hi colleagues,
in-place upgrade from 6.7 to 7.4 had been discussed as mitigation to a perhaps delayed certification of RHEL 6.10 by SAP. To my understanding, outcome of this assessment had been, that in-place upgrade is not viable for this use case. This is because in-place upgrade would be via RHEL 6.10 (hence without undo ability) and also not sufficient tested for application layer of SAP. We hence made the decision to raise priority of RHEL 6.10 certification by SAP and not to position in-place upgrade as Red Hat's recommended path for customers currently on RHEL 6.7.
Arne
Comment 13 Daniel Yeisley 2018-11-29 18:25:21 UTC 
I installed HANA 1.0 on a system running RHEL-6.10 and executed my test against it. Then I installed the preupgrade-assistant RPMs from brew and did the upgrade to RHEL-7.4. After a reboot I started HANA and ran my test against it again. I didn't see any issues.

I used the following RPMs. 
preupgrade-assistant-el6toel7-sap-0.7.3-4.el6_10.noarch.rpm  
preupgrade-assistant-el6toel7-sap-data-0.20180503-1.el6.noarch.rpm
Comment 15 errata-xmlrpc 2019-01-16 09:14:44 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/RHEA-2019:0070
Note You need to log in before you can comment on or make changes to this bug.