How nondisruptive update works

When you remediate the inconsistencies of the member hypervisor profiles using the hypervisor cluster profile, the inconsistencies in all the cluster members that are powered on and active are fixed in a sequential manner. The nondisruptive update repeats the following sequence until all the cluster members are updated to match the template configurations and are consistent.

Picks up a hypervisor.
Moves the hypervisor to maintenance state. This movement ensures all the workloads and data are moved to other hosts in the cluster.
Remediates the inconsistencies in the corresponding cluster member. First, remediates the inconsistencies in the corresponding server profile to update the physical server configurations, and then remediates the inconsistencies in the corresponding hypervisor profile to update the hypervisor configurations.
Moves the hypervisor back to active state. If the hypervisor was in maintenance state before applying the update, the hypervisor is retained in maintenance state.
Picks up the next hypervisor in the cluster.

If there is a failure during the update, the hypervisor cluster profile aborts the sequential update flow and moves the task to error state. Review the error, and initiate the remediation again only after you resolve the error. If the failure occurred while updating one of the cluster members, the hypervisor cluster profile leaves the failed hypervisor in maintenance state.