Bug 1382636 - Upgrade from v3.2 to v3.3 fails since oadm-command is deprecated
Summary: Upgrade from v3.2 to v3.3 fails since oadm-command is deprecated
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Cluster Version Operator
Version: 3.3.0
Hardware: Unspecified
OS: Unspecified
urgent
high
Target Milestone: ---
: 3.3.1
Assignee: Devan Goodwin
QA Contact: Anping Li
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-10-07 09:14 UTC by Jaspreet Kaur
Modified: 2019-12-16 07:01 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Cause: oadm symlink incorrectly pointing to "oc" rather than "openshift" binary on containerized master hosts. Consequence: Upgrade fails complaining about missing oadm functionality. Fix: Transitioned to use of "oc adm" throughout playbooks. Result: Upgrade will now pass in these environments.
Clone Of:
Environment:
Last Closed: 2016-10-27 16:13:55 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2016:2122 0 normal SHIPPED_LIVE OpenShift Container Platform atomic-openshift-utils bug fix update 2016-10-27 20:11:30 UTC

Comment 4 Trine Lise Åvik 2016-10-17 11:29:30 UTC 
Possible fix:

When changing
"{{ openshift.common.admin_binary}}"
to
"{{ openshift.common.client_binary}} adm" 
in the upgrade-playbook,
https://github.com/openshift/openshift-ansible/blob/openshift-ansible-3.3.22-1/playbooks/common/openshift-cluster/upgrades/upgrade.yml, the upgrade from v3.2 to v3.3 (containerized) completed successfully.
Comment 6 Devan Goodwin 2016-10-19 13:45:53 UTC 
Attempted fix using customer's workaround which should be valid in all cases: https://github.com/openshift/openshift-ansible/pull/2621
Comment 8 Anping Li 2016-10-20 04:43:22 UTC 
Verified and pass using atomic-openshift-utils-3.3.38-1
Comment 10 errata-xmlrpc 2016-10-27 16:13:55 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-2016:2122
Note You need to log in before you can comment on or make changes to this bug.