Moving upgrade portion to a new bug.
Merged to release-3.10, https://github.com/openshift/openshift-ansible/pull/9615
Basic process for manually switching a node from system container to rpm cri-o: oc adm manage-node $NODE --schedulable=false oc adm drain $NODE --force --delete-local-data --ignore-daemonsets systemctl stop atomic-openshift-node.service systemctl stop cri-o.service atomic uninstall cri-o # Delete the crio system container image so we know it's not being used atomic images delete $CRIO-IMAGE yum install -y cri-o # Ensure we have the latest systemd units loaded systemctl daemon-reload # Ensure the latest one is enabled at reboot systemctl enable cri-o.service systemctl start cri-o.service systemctl start atomic-openshift-node.service
1. Install openshift v3.9.30 with following inventory parameters: openshift_crio_systemcontainer_image_override=test.registry.com/openshift3/cri-o:v3.9 openshift_use_crio=true 2. Upgrade to v3.10.34 using openshift-ansible-3.10.34-1.git.0.48df172None.noarch 3. Upgrade succeed, system container cri-o is transferred to rpm cri-o successfully 4. Existing app works well, new created app works well Moving to verified.
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:2376