Bug 1548485 - Upgrade from 3.7 to 3.9 fails
Summary: Upgrade from 3.7 to 3.9 fails
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: OpenShift Container Platform
Classification: Red Hat
Component: Installer
Version: 3.9.0
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: 3.9.0
Assignee: Michael Gugino
QA Contact: Johnny Liu
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-02-23 16:23 UTC by Vikas Laad
Modified: 2018-03-28 14:30 UTC (History)
5 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-03-28 14:30:19 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2018:0489 0 None None None 2018-03-28 14:30:51 UTC

Description Vikas Laad 2018-02-23 16:23:51 UTC
Description of problem:

Trying to upgrade from 3.7 cluster to 3.9 cluster fails with following error

TASK [openshift_master : include_tasks] *********************************************************************************************************************$
task path: /root/openshift-ansible/roles/openshift_master/tasks/upgrade.yml:2
included: /root/openshift-ansible/roles/openshift_master/tasks/upgrade/rpm_upgrade.yml for ec2-35-161-124-109.us-west-2.compute.amazonaws.com

TASK [openshift_master : Upgrade master packages - yum] *****************************************************************************************************$
task path: /root/openshift-ansible/roles/openshift_master/tasks/upgrade/rpm_upgrade.yml:11
fatal: [ec2-35-161-124-109.us-west-2.compute.amazonaws.com]: FAILED! => {
    "msg": "Version comparison: 'openshift_release' is undefined"
}
        to retry, use: --limit @/root/openshift-ansible/playbooks/byo/openshift-cluster/upgrades/v3_9/upgrade.retry

PLAY RECAP **************************************************************************************************************************************************$
ec2-35-161-124-109.us-west-2.compute.amazonaws.com : ok=197  changed=14   unreachable=0    failed=1   
localhost                  : ok=19   changed=0    unreachable=0    failed=0   


Version-Release number of the following components:
rpm -q openshift-ansible 
openshift-ansible-3.7.28-1.git.0.12b5132.el7.noarch

rpm -q ansible
ansible-2.4.2.0-2.el7.noarch

ansible --version
ansible 2.4.2.0
  config file = /etc/ansible/ansible.cfg
  configured module search path = [u'/root/.ansible/plugins/modules', u'/usr/share/ansible/plugins/modules']
  ansible python module location = /usr/lib/python2.7/site-packages/ansible
  executable location = /usr/bin/ansible
  python version = 2.7.5 (default, Dec  8 2017, 16:39:59) [GCC 4.8.5 20150623 (Red Hat 4.8.5-25)]

How reproducible:
Always

Steps to Reproduce:
1. Create 3.7 cluster
2. upgrade to 3.9 with v3_9 playbook, inventory attached.

Actual results:
Please include the entire output from the last TASK line through the end of output if an error is generated

Expected results:
Playbook fails

Additional info:
Please attach logs from ansible-playbook with the -vvv flag

Comment 1 Michael Gugino 2018-02-23 16:27:02 UTC
PR Created: https://github.com/openshift/openshift-ansible/pull/7269

Comment 3 Scott Dodson 2018-02-26 14:55:36 UTC
*** Bug 1549081 has been marked as a duplicate of this bug. ***

Comment 4 Vikas Laad 2018-02-26 15:33:09 UTC
I do not see this error anymore when running upgrade from 3.7 to 3.9

Comment 7 errata-xmlrpc 2018-03-28 14:30:19 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-2018:0489


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