Bug 1173713

Summary:	redhat-upgrade-tool is fundamentally broken without using distro-sync
Product:	Red Hat Enterprise Linux 6	Reporter:	Orion Poplawski <orion>
Component:	redhat-upgrade-tool	Assignee:	David Shea <dshea>
Status:	CLOSED CURRENTRELEASE	QA Contact:
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	6.6	CC:	fkluknav, ovasik, phracek, ttomecek
Target Milestone:	rc	Keywords:	Extras, Reopened
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-01-05 14:49:14 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

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.