Bug 1433378

Description of problem:

While trying to update to the latest 3.2 version using asynchronous upgrade procedure running the ansible-playbook like this:  /usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/upgrades/v3_2/upgrade.yml, the playbook fails with the following error:

ASK [Verify Ansible version is greater than or equal to 2.1.0.0] **************
skipping: [localhost]
... ... ... 
TASK [openshift_facts] *********************************************************
fatal: [master.example.com]: FAILED! => {"failed": true, "msg": "the field 'args' has an invalid value, which appears to include a variable that is undefined. The error was: 'dict object' has no attribute 'oo_etcd_to_config'\n\nThe error appears to have been in '/usr/share/ansible/openshift-ansible/playbooks/common/openshift-cluster/upgrades/pre.yml': line 243, column 5, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n  tasks:\n  - openshift_facts:\n    ^ here\n"}
        to retry, use: --limit @/usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/upgrades/v3_2/upgrade.retry

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

openshift-ansible-3.2.47-1.git.0.34a924d.el7.noarch
atomic-openshift-utils-3.2.47-1.git.0.34a924d.el7.noarch

How reproducible:

Always.

Steps to Reproduce:
1. Follow official documentation steps for doing an asynchronous upgrade through the ansible-playbook

2. Running the ansible playbook like this:  ansible-playbook -i /etc/ansible/hosts /usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/upgrades/v3_2/upgrade.yml


Actual results:
The error described above.

Expected results:
Async upgrade performed without issues.

Additional info:

The ansible hosts used is like this:

# Create an OSEv3 group that contains the masters and nodes groups
[OSEv3:children]
masters
nodes
#new_nodes

# Set variables common for all OSEv3 hosts
[OSEv3:vars]

# SSH user, this user should allow ssh based auth without requiring a password
ansible_ssh_user=root

# If ansible_ssh_user is not root, ansible_sudo must be set to true
#ansible_sudo=true
deployment_type=openshift-enterprise
osm_use_cockpit=true
osm_default_node_selector="region=primary"
osm_default_subdomain=cloudapps.example.com
osm_cluster_network_cidr=11.1.0.0/16
openshift_node_kubelet_args={'minimum-container-ttl-duration': ['10s'],'maximum-dead-containers-per-container': ['2'],'maximum-dead-containers': ['10'],'image-gc-high-threshold': ['90'],'image-gc-low-threshold': ['80']}

# '': [''],

# uncomment the following to enable htpasswd authentication; defaultsto DenyAllPasswordIdentityProvider
openshift_master_identity_providers=[{'name': 'htpasswd_auth','login': 'true', 'challenge': 'true', 'kind':'HTPasswdPasswordIdentityProvider', 'filename':'/etc/origin/openshift-passwd'}]

# host group for masters
[masters]
master.example.com

# host group for nodes, includes region info
[nodes]
master.example.com openshift_node_labels="{'region': 'infra', 'zone': 'default'}"
node1.example.com openshift_node_labels="{'region': 'primary', 'zone': 'east'}"
node2.example.com openshift_node_labels="{'region': 'primary', 'zone': 'west'}"
#[new_nodes]
#node3.example.com openshift_node_labels="{'region': 'primary', 'zone': 'west'}"


The same result is happening with the latest atomic-openshift-utils package:

atomic-openshift-utils-3.2.53-1.git.0.2fefc17.el7.noarch