5 Patching Individual Components

The granular patching mechanism allows you to perform patching procedures for individual hardware and software components. In separate workflows, you patch the compute nodes, the management node cluster and the controller software components running on it, different categories of firmware, and Oracle Cloud Infrastructure images.

Note:

In software version 3.0.2-b892153 and later the Upgrader service uses the upgrade plan, generated during the pre-upgrade process, to determine whether a component needs to be patched. If a component is already at the required version, the patch command does start an upgrade/patch job, but it is completed immediately because the upgrade plan indicates there is nothing to do.

Practically speaking, when a component is already at the required version, the patch procedure is skipped. However, a same-version patch can be forced using the Service Web UI or Service CLI command option, if necessary. For example: patchKubernetes force=True.

All components must be patched in a prescribed order. A component can only be patched on condition that the preceding components in the list are already at the required version. The upgrade plan will prevent a component patch procedure from starting if the preceding patch operations have not been completed. For more information, see Check Upgrade Plan Status and Progress.