TASK [set_fact] **************************************************************** Wednesday 09 May 2018 21:03:54 +0000 (0:00:00.104) 0:00:08.970 ********* fatal: [free-int-master-3c664]: FAILED! => {"msg": "The field 'vars' has an invalid value, which includes an undefined variable. The error was: 'dict object' has no attribute 'clusterNetworks'\n\nThe error appears to have been in '/home/opsmedic/aos-cd/tmp/openshift-ansible-bqFMlq/playbooks/init/basic_facts.yml': line 84, column 5, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n - set_fact:\n ^ here\n\nexception type: <class 'ansible.errors.AnsibleUndefinedVariable'>\nexception: 'dict object' has no attribute 'clusterNetworks'"} fatal: [free-int-master-de987]: FAILED! => {"msg": "The field 'vars' has an invalid value, which includes an undefined variable. The error was: 'dict object' has no attribute 'clusterNetworks'\n\nThe error appears to have been in '/home/opsmedic/aos-cd/tmp/openshift-ansible-bqFMlq/playbooks/init/basic_facts.yml': line 84, column 5, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n - set_fact:\n ^ here\n\nexception type: <class 'ansible.errors.AnsibleUndefinedVariable'>\nexception: 'dict object' has no attribute 'clusterNetworks'"} fatal: [free-int-master-5470f]: FAILED! => {"msg": "The field 'vars' has an invalid value, which includes an undefined variable. The error was: 'dict object' has no attribute 'clusterNetworks'\n\nThe error appears to have been in '/home/opsmedic/aos-cd/tmp/openshift-ansible-bqFMlq/playbooks/init/basic_facts.yml': line 84, column 5, but may\nbe elsewhere in the file depending on the exact syntax problem.\n\nThe offending line appears to be:\n\n\n - set_fact:\n ^ here\n\nexception type: <class 'ansible.errors.AnsibleUndefinedVariable'>\nexception: 'dict object' has no attribute 'clusterNetworks'"}
PR Created: https://github.com/openshift/openshift-ansible/pull/8325
I assume the reproducible step is to create 3.6 cluster, then upgrade to 3.10 step by step.
(In reply to Gan Huang from comment #4) > I assume the reproducible step is to create 3.6 cluster, then upgrade to > 3.10 step by step. Yes, or make some edits to the master config file outside of openshift-ansible; the deprecated values should still function correctly.
Install 3.9 cluster, and remove the following lines from master-config.yaml > clusterNetworks: > - cidr: 10.128.0.0/14 > hostSubnetLength: 9 Then upgrade to 3.10 by using openshift-ansible-3.10.0-0.47.0.git.0.c018c8f.el7.noarch.rpm successfully.
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:1816