Hi, Deploying or upgrading to 3.11, I'ld go with ansible 2.6. Currently, the ansible package provided by RedHat is some 2.6.16-1. Personally, I'm still using 2.6.5, from PIP. I'm not sure 2.7 is actually supported.
To upgrade an existing installation, one would usually: - check the release notes ( https://docs.openshift.com/container-platform/3.11/release_notes/ocp_3_11_release_notes.html ) - update your inventory accordingly (remove deprecated variables, add what you'ld need, ...) - follow the in-place cluster upgrades procedure ( https://docs.openshift.com/container-platform/3.11/upgrading/automated_upgrades.html ) Sometimes, upgrading could have difficulties detecting either current or target versions, don't hesitate setting them yourself: openshift_image_tag: v3.11 openshift_pkg_version: -3.11.0 openshift_release: v3.11 openshift_upgrade_min: 3.11 openshift_version: "3.11" Once your variables are ready, you should be able to apply the upgrade_control_plane and upgrade_nodes playbooks: ansible-playbook -i </path/to/inventory/file> ./playbooks/byo/openshift-cluster/upgrades/v3_11/upgrade_control_plane.yml ansible-playbook -i </path/to/inventory/file> ./playbooks/byo/openshift-cluster/upgrades/v3_11/upgrade_nodes.yml Now, regarding your error, it sounds like ansible isn't able to properly detect the version of openshift currently deployed. That version should be extracted via roles/lib_utils/library/get_current_openshift_version.py, around line 74, grepping for an IMAGE_VERSION= in /etc/sysconfig/origin-node Note that upgrading, you shouldn't have to apply the prerequisites playbook. Yet it should work. If you can't get it to work, then try forcing IMAGE_VERSION=v3.10 in /etc/sysconfig/origin-node. Let us know how that goes. Regards. On Wed, Apr 17, 2019 at 2:27 PM Hyde Stevenson <[email protected]> wrote: > Hello, > > We have an OKD 3.10 cluster and I wouli like to migrate to the new > 3.11 version but got a couple of questions : > > - is there a specific ansible version to use ? I know from my past > experience that for x version you must use a specific version. > The README indicates that it must be >= 2.6 and that the 2.7 is > supported ... but which one exactly ? > > - What is the best way to migrate the masters and nodes ? Should I > remove them one by one from the cluster and migrate them ? > > Play: Ensure firewall is not switched during upgrade > Task: set currently installed version > Message: The task includes an option with an undefined variable. The > error was: 'ansible.vars.hostvars.HostVarsVars object' has no attribute > 'openshift_current_version' > > The error appears to have been in > 'openshift-ansible/playbooks/common/openshift-cluster/upgrades/init.yml': > line 24, column 5, but may > be elsewhere in the file depending on the exact syntax > problem. > > The offending line appears to be: > > tasks: > - name: set currently installed version > ^ here > > Any idea about that error ? > > -- > Hyde Stevenson > > Don't guess -- check your security regulations. > _______________________________________________ > users mailing list > [email protected] > http://lists.openshift.redhat.com/openshiftmm/listinfo/users > -- Samuel Martín Moro {EPITECH.} 2011 "Nobody wants to say how this works. Maybe nobody knows ..." Xorg.conf(5)
_______________________________________________ users mailing list [email protected] http://lists.openshift.redhat.com/openshiftmm/listinfo/users
