Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1097928

Summary:	/usr/bin/oo-admin-yum-validator --oo-version 2.1 --fix-all requires manual intervention for RHN Classic
Product:	OpenShift Container Platform	Reporter:	Brenton Leanhardt <bleanhar>
Component:	Cluster Version Operator	Assignee:	John W. Lamb <jolamb>
Status:	CLOSED NOTABUG	QA Contact:	libra bugs <libra-bugs>
Severity:	medium	Docs Contact:
Priority:	medium
Version:	2.0.0	CC:	jokerman, libra-onpremise-devel, mmccomas, pep, perobins
Target Milestone:	---	Keywords:	ZStream
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2014-07-01 13:49:36 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 Brenton Leanhardt 2014-05-14 21:39:13 UTC

Description of problem:

Currently if '/usr/bin/oo-admin-yum-validator --oo-version 2.1 --fix-all' is run it will not subscribe a system to the 2.1 channels but instead will report the manual steps required.

It is important to note that once the channels are manually subscribed running the command again will set the priorities and excludes as expected.

Comment 1 Brenton Leanhardt 2014-05-14 21:43:05 UTC

This is most often noticed on an OpenShift Enterprise 2.0 installation from RHN Classic.  When 'ose-upgrade begin' is run to start the upgrade process to 2.1 this command will fail and halt the upgrade until the manual steps are run.

Comment 2 John W. Lamb 2014-07-01 13:49:36 UTC

This isn't a bug; oo-admin-yum-validator guarantees appropriate priorities for the repos and make certain that the needed *subscribed* repos/channels are enabled, but it is up to the user (or the ose-upgrade tool) to actually subscribe the appropriate repos/channels.

I'm not certain if ose-upgrade still exhibits the described behavior; I'll try to test that today.