// Module included in the following assemblies:
//
// * updating/updating_a_cluster/update-using-custom-machine-config-pools.adoc

:_mod-docs-content-type: PROCEDURE
[id="update-using-custom-machine-config-pools-unpause_{context}"]
= Unpausing the machine config pools

[role="_abstract"]
After the {product-title} update is complete, unpause your custom machine config pools (MCP) one at a time. Unpausing an MCP allows the Machine Config Operator (MCO) to update the nodes associated with that MCP.

.Procedure

. Patch the MCP that you want to unpause:
+
[source,terminal]
----
$ oc patch mcp/<mcp_name> --patch '{"spec":{"paused":false}}' --type=merge
----
+
For example:
+
[source,terminal]
----
$  oc patch mcp/workerpool-canary --patch '{"spec":{"paused":false}}' --type=merge
----
+
.Example output
+
[source,terminal]
----
machineconfigpool.machineconfiguration.openshift.io/workerpool-canary patched
----

. Optional: Check the progress of the update by using one of the following options:

.. Check the progress from the web console by clicking *Administration* -> *Cluster settings*.

.. Check the progress by running the following command:
+
[source,terminal]
----
$ oc get machineconfigpools
----

. Test your applications on the updated nodes to ensure that they are working as expected.

. Repeat this process for any other paused MCPs, one at a time.
+
[NOTE]
====
In case of a failure, such as your applications not working on the updated nodes, you can cordon and drain the nodes in the pool, which moves the application pods to other nodes to help maintain the quality-of-service for the applications. This first MCP should be no larger than the excess capacity.
====
