OS Package Update
To install multiple packages on target nodes in a bulk operation, the package_update.yml
playbook can be leveraged.
Prerequisites
All target nodes should be running RHEL or Rocky.
Download the packages (RPMs) for the target nodes and place them in this folder:
/install/post/otherpkgs/<Provision OS.Version>/x86_64/custom_software/Packages
.Note
Do not use ISO files for updates or package installations.
Create a package list by creating the following text file (For packages that are not in RHEL repos, name the file
update.otherpkgs.pkglist
. For OS packages,xxxx.pkglist
) and place in the default path. For example:/install/post/otherpkgs/<Provision OS.Version>/x86_64/custom_software/update.otherpkgs.pkglist
:custom_software/<package1>-<version1> custom_software/<package2>-<version2> custom_software/<package3>-<version3>
To customize the package update, enter the following parameters in utils/package_update_config.yml
:
Parameter |
Details |
---|---|
|
The operating system in use on the target cluster nodes.
|
|
OS version of target nodes in the cluster. Default value: 8.6 |
|
Default value: |
|
Choices:
|
|
comma-separated list of all target nodes in the cluster.
|
|
Indicates whether the remote nodes listed will be rebooted. Choices:
|
To run the playbook, run the following commands:
cd utils
ansible-playbook package_update.yml
Note
At the end of the playbook, the package update status is displayed by target node. If the update status of any node is failed
, use the command log (/var/log/xcat/commands.log
) to debug the issue. Alternatively, verify that the node is reachable post provisioning.
If you have any feedback about Omnia documentation, please reach out at omnia.readme@dell.com.