Bug 1299055 - yum erase erased too much in the upgrade process
Summary: yum erase erased too much in the upgrade process
Keywords:
Status: CLOSED DUPLICATE of bug 1299056
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cluster Version Operator
Version: 2.1.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: Timothy Williams
QA Contact: Anping Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-01-15 20:11 UTC by Eric Jones
Modified: 2019-10-10 10:54 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
OpenShift Enterprise 2.1
Last Closed: 2016-05-31 15:06:03 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)

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 ***


Note You need to log in before you can comment on or make changes to this bug.