Description of problem: If the openshift_master_portal_net is inventory file, those values expected for '--selinux-enabled ' will be deleted in OPTIONS in /etc/sysconfig/docker on master after upgrade. Version-Release number of selected component (if applicable): atomic-openshift-utils-3.0.94-1.git.0.67a822a.el7.noarch atomic-openshift-utils-3.2.1-1.git.0.b8d1b5e.el7 How reproducible: always Steps to Reproduce: 1) Enable osm_cluster_network_cidr="10.2.0.0/16" and penshift_master_portal_net="172.31.0.0/16" install OSE 3.0.2.0 by atomic-openshift-utils-3.0.35-1.git.0.6a386dd.el7aos.noarch 2) check the docker configuration file on master grep OPTIONS /etc/sysconfig/docker 3) upgrade to OSE 3.1 ansible-playbook -i config/hosts /usr/share/ansible/openshift-ansible/playbooks/byo/openshift-cluster/upgrades/v3_0_to_v3_1/upgrade.yml -vvv|tee upgradev30tov31.logs2.logs ##Note: upgrade to docker 1.10 before run upgrade playbook if you are using atomic-openshift-utils-3.2.1 4) check the docker configuration file on master grep OPTIONS /etc/sysconfig/docker Actual results: 2)#grep OPTIONS /etc/sysconfig/docker OPTIONS=' --selinux-enabled --insecure-registry=172.31.0.0/16 ' 4)#grep OPTIONS /etc/sysconfig/docker OPTIONS=' --selinux-enabled' Expected results: --insecure-registry should be added to OPTIONS Additional info:
Is this specific to the 3.0->3.1 upgrade? or does it happen with 3.1->3.2 as well?
Only for the 3.0->3.1 upgrade?
I think this is caused by using the 3.2 playbooks with 3.0. We're now going to require that the version of openshift-ansible match the installed environment or the version you wish to upgrade to.
Closing as this install/upgrade path is not supported in the 3.2 version of the playbooks.