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 1173713 - redhat-upgrade-tool is fundamentally broken without using distro-sync
Summary: redhat-upgrade-tool is fundamentally broken without using distro-sync
Keywords:
Status: CLOSED CURRENTRELEASE
Alias: None
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: redhat-upgrade-tool
Version: 6.6
Hardware: All
OS: Linux
unspecified
high
Target Milestone: rc
: ---
Assignee: David Shea
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2014-12-12 18:28 UTC by Orion Poplawski
Modified: 2015-01-05 14:49 UTC (History)
4 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-01-05 14:49:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description Orion Poplawski 2014-12-12 18:28:53 UTC 
Description of problem:

Without using distro-sync, the redhat-upgrade-tool process is fundamentally broken.  For example, the tool currently reports:

INPLACERISK: MEDIUM: having one of [libxcb libX11-common libdrm mdadm tzdata libbasicobjects nss-tools sssd-client sssd-ipa sssd-proxy sssd nspr audit-libs-python nss-util nss-sysinit libsss_idmap sssd-common sssd-common-pac sssd-ad sssd-krb5 python-sssdconfig openscap libX11 systemtap-runtime audit audit-libs elfutils-libelf libref_array elfutils ca-certificates libini_config biosdevname kpartx elfutils-libs nss libipa_hbac sssd-krb5-common libpciaccess sssd-ldap openldap] package installed breaks upgrade

One big killer here is openldap:

2.4.39-8.el6 -> 2.4.39-3.el7

The el6 version uses libsasl2.so.2, while the new cyrus-sasl-lib provides libsasl2.so.3.  After upgrade this breaks (at least) python (and there for yum) and ssh which makes it extremely difficult to repair the system. 

Fedora (https://fedoraproject.org/wiki/Upgrading_Fedora_using_yum) has always recommended using distro-sync.

I at least see it in your TODO list: https://github.com/dashea/redhat-upgrade-tool/blob/0ebb90bbbfb3dec3f86876ec664cbb4699646208/TODO.asciidoc

Version-Release number of selected component (if applicable):
redhat-upgrade-tool-0.7.32-1.el6.noarch
Comment 2 David Shea 2014-12-12 21:15:16 UTC 
While Red Hat welcomes bug reports on Red Hat products here in our public
bugzilla database, please keep in mind that bugzilla is not a support tool or
means of accessing support.  If you would like technical support please visit
our support portal at access.redhat.com or call us for information on
subscription offerings to suit your needs.
Comment 3 Ondrej Vasik 2014-12-15 11:11:41 UTC 
Orion, thanks for the report. Actually, thanks to preupgrade-assistant modules, we are able to deal with package downgrades quite well - these extend the fedup functionality. You are right these are really tricky without distrosync.
We believe preupgrade-assistant-contents are able to handle latest->latest upgrade for server scenarios even for the cases like you mentioned (libsasl soname difference). If you don't think this is true, please provide sosreport and description of your setup and report the bugzilla against preupgrade-assistant-contents.
Comment 4 Petr Hracek 2014-12-15 11:46:04 UTC 
Hello David,

this is not a good approach to close bugzilla.
We should solve the problem with libsasl library because of
it is repeated several time. Even during each new release.

Please try to solve the problem with redhat-upgrade-tool.
Do not reassign the problem to preupgrade-assistant-contents.
Both tools should solve the problem. And we should find the way.

Orion, 
could you please mentioned what versions of packages you have?
Especially preupgrade-assistant and preupgrade-assistant-contents.

We should solve the problem, though.
Comment 5 Orion Poplawski 2014-12-15 16:27:26 UTC 
Versions:
redhat-upgrade-tool-0.7.32-1.el6.noarch
preupgrade-assistant-2.0.1-1.el6.x86_64
preupgrade-assistant-contents-0.6.7-5.el6.noarch

Some general comments:

- The only reason the current fedup approach works for Fedora (most of the time, and not without controversy - see bug #892061) is that Fedora has a policy that every package in Fedora N+1 must be greater in version than Fedora N.  This does not appear to be the case in RHEL.

- Looking at the result.html from preupgrade assistant, I do not see any red flags about the openldap issue.  In particular, I do NOT see the message I posted in the original report there, only when running redhat-upgrade-tool.  That being missing from that report may be a separate issue with the pre-upgrade tool - filed bug #1174335.
Comment 6 Orion Poplawski 2014-12-23 22:02:00 UTC 
Please accept my sincerest apologies - I ran the test using the CentOS upgrade tool and made the incorrect assumption that the redhat tool was the same.  Testing with the redhat tool worked fine.
Comment 7 David Shea 2015-01-05 14:49:14 UTC 
Good to hear.
Note You need to log in before you can comment on or make changes to this bug.