Description of problem: This may already be implemented but we ought to document and test it thoroughly (e.g. verifying that any existing pods get moved away before we delete the nodes)
In order to remove a specific node, follow these steps: a) In OpenShift, do the following as described in https://docs.openshift.com/enterprise/3.0/admin_guide/manage_nodes.html i) Mark the node as unschedulable ii) Evacuate the node iii) Delete the node b) Remove App Node from OpenStack: specify openshift_openstack_nodes_to_remove in your inventory as described in https://github.com/openshift/openshift-ansible/blob/master/playbooks/openstack/advanced-configuration.md
This has bee implemented in 3.10.
Per OCP program call on 21-SEP-2018 we are deferring Kuryr-related bugs to 3.11.z
Checked with openshift-ansible-3.11.57-1 and replacing specific node work well. openshift_openstack_nodes_to_remove: ['2'] ansible-playbook --private-key ~/.ssh/libra-new.pem --user openshift -i openshift-ansible/playbooks/openstack/scaleup_inventory.py -i inventory openshift-ansible/playbooks/openstack/openshift-cluster/node-scaleup.yml -vv [openshift@master-0 ~]$ oc get nodes NAME STATUS ROLES AGE VERSION app-node-0.wjiang-ocp.example.com Ready,SchedulingDisabled compute 1h v1.11.0+d4cacc0 app-node-1.wjiang-ocp.example.com Ready compute 1h v1.11.0+d4cacc0 infra-node-0.wjiang-ocp.example.com Ready infra 1h v1.11.0+d4cacc0 master-0.wjiang-ocp.example.com Ready master 1h v1.11.0+d4cacc0 master-1.wjiang-ocp.example.com Ready master 1h v1.11.0+d4cacc0 [openshift@master-0 ~]$ oc get nodes NAME STATUS ROLES AGE VERSION app-node-1.wjiang-ocp.example.com Ready compute 1h v1.11.0+d4cacc0 app-node-2.wjiang-ocp.example.com Ready compute 3m v1.11.0+d4cacc0 infra-node-0.wjiang-ocp.example.com Ready infra 1h v1.11.0+d4cacc0 master-0.wjiang-ocp.example.com Ready master 1h v1.11.0+d4cacc0 master-1.wjiang-ocp.example.com Ready master 1h v1.11.0+d4cacc0 [openshift@master-0 ~]$ oc get nodes NAME STATUS ROLES AGE VERSION app-node-1.wjiang-ocp.example.com Ready compute 1h v1.11.0+d4cacc0 app-node-3.wjiang-ocp.example.com NotReady compute 11s v1.11.0+d4cacc0 infra-node-0.wjiang-ocp.example.com Ready infra 1h v1.11.0+d4cacc0 master-0.wjiang-ocp.example.com Ready master 1h v1.11.0+d4cacc0 master-1.wjiang-ocp.example.com Ready master 1h v1.11.0+d4cacc0
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-2019:0024