You can start viewing available patches and applying them to your nodes using the
pe_patch::patch_server task after you have set up patch
management. Review optional parameters for the
task prior to running it.
Select patches and then apply them by running the
pe_patch::patch_server task. Limit patches to security or non-security
updates, Windows or *nix nodes,
or a specific patch group.
pe_patch::patch_servertask is what applies patches and optionally reboots the selected nodes.
On the Patches page, in the Apply
patches section, use the filters to specify which patches to
apply to which nodes.
Note: Filters use
andlogic. This means that if you select Security updates and Windows, the results include security patches for Windows nodes, not all security patches and all Windows patches.
Select Run > Task.
The Run a task page appears with patching information pre-filled for the
- Optional: In the Job details field, provide a description of the task run. This appears on the Tasks page.
Under Task parameters, add optional parameters to the
task. See Patching task parameters for a full list of available
Note: You must click Add parameter for each optional parameter-value pair you add to the task.
- Optional: If you want to schedule the task to run later, under Schedule, select Later and choose a time.
- Select Run task to apply patches.
pe_patchfact to verify the relevant packages were updated.
Patching task parameters
pe_patch::patch_server task applies patches to
nodes. When you patch nodes in the console, most of the information for the
patch_server task is prefilled on the Run a
task page, but you can add additional parameters to the task before you run
it. Here are the optional parameters to review before you run the patching task.
- Determines if the server should reboot after applying patches. [Boolean,
always- The node always reboots during the task run, even if no patches are required.
false) - The node never reboots during the task run, even if patches are applied.
true) - The node reboots if patches are applied.
smart- Use the OS supplied tools, like
needs_restartingon RHEL or a pending reboot check on Windows, to determine if a reboot is required, if it is reboots, or if it does not reboot.
- Determines how many seconds before the task run times out. Integer.
- Indicates what additional parameters to include in the yum upgrade command, such as including or excluding repos. String.
- Indicates if the yum/dpkg caches are cleaned at the start of the task. Boolean.
- Indicates what additional parameters to include in the dpkg command. String.
- Determines whether to include only security patches in a task run. Boolean.
- Indicates what additional parameters to include in the zypper update command. String.