Bug 1463139 - [3.4]Failed to detect new openshift version due to miss cleaning yum repo during upgrade
Summary: [3.4]Failed to detect new openshift version due to miss cleaning yum repo dur...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cluster Version Operator
Version: 3.4.1
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: ---
: 3.4.z
Assignee: Russell Teague
QA Contact: liujia
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-06-20 08:40 UTC by liujia
Modified: 2017-06-29 13:33 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
If the installer does not process a change to configured repos it will not refresh the cache. The fix will force a cache refresh in situations where repos were manually changed prior to running the upgrade.
Clone Of:
Environment:
Last Closed: 2017-06-29 13:33:14 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2017:1666 0 normal SHIPPED_LIVE OpenShift Container Platform atomic-openshift-utils bug fix and enhancement 2017-06-29 17:32:39 UTC

Comment 1 Russell Teague 2017-06-20 17:37:58 UTC 
Proposed: https://github.com/openshift/openshift-ansible/pull/4513
Comment 2 Russell Teague 2017-06-21 19:19:06 UTC 
Merged: https://github.com/openshift/openshift-ansible/pull/4513
Comment 4 liujia 2017-06-27 06:15:24 UTC 
Version:
atomic-openshift-utils-3.4.108-1.git.0.6b32ddc.el7.noarch

Steps:
1. Install ocp3.3
2. Prepare 3.4 repo with the same name as original 3.3 repo
3. Run upgrade playbook

Upgrade succeed.
Comment 6 errata-xmlrpc 2017-06-29 13:33:14 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2017:1666
Note You need to log in before you can comment on or make changes to this bug.