Bug 1299055

Summary:	yum erase erased too much in the upgrade process
Product:	OpenShift Container Platform	Reporter:	Eric Jones <erjones>
Component:	Cluster Version Operator	Assignee:	Timothy Williams <tiwillia>
Status:	CLOSED DUPLICATE	QA Contact:	Anping Li <anli>
Severity:	high	Docs Contact:
Priority:	unspecified
Version:	2.1.0	CC:	aos-bugs, erjones, jokerman, mmccomas, rthrashe, tiwillia
Target Milestone:	---
Target Release:	---
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:	OpenShift Enterprise 2.1
Last Closed:	2016-05-31 15:06:03 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:

Description Eric Jones 2016-01-15 20:11:37 UTC

Description of problem:
Running `ose-upgrade rpms` per the upgrade (2.1->2.2) procedure removes node cartridge packages as well as the rest of the upgrade files, causing the next step `ose-upgrade conf` to fail.

Version-Release number of selected component (if applicable):
2.1 upgrade

How reproducible:
Unsure as of yet

Steps to Reproduce:
1. Follow the upgrade (2.1->2.2) documentation.
2. Run ose-upgrade rpms
3. Run ose-upgrade conf

Actual results:
ose-upgrade conf fails  stating:
# ose-upgrade conf
ERROR: run_upgrade_step
The 'conf' upgrade step is not implemented for this host

As well as removing node cartridge packages

Expected results:
Upgrade of the configuration occurs and it tells you the next step to upgrade.

Comment 3 Eric Jones 2016-05-31 15:06:03 UTC

@Rory, I'm not really sure why both this bug and #1299056 exist separately...We can close this one in favor of that one, as Tim apparently did _some_ work on that one.

*** This bug has been marked as a duplicate of bug 1299056 ***