Obtaining systemd update for system upgrades

For new system installation, the systemd update is shipped with the system and it is available in the /home/deploy directory. However, for upgrades, you need to obtain and package the systemd update, and then install the systemd update.

You must have a EUS license to download the systemd update from Red Hat Network.

Use the following steps during an upgrade to obtain and package the systemd update.

Clear the version locks.
```
yum versionlock clear
```

Connect the management server node to the Red Hat Network.

subscription-manager register --username=<X> --password=<Y>
subscription-manager list --available // list pools
subscription-manager attach --pool=<X>

subscription-manager attach --auto

Create a directory for the systemd update package.
For PPC64BE, issue:
```
mkdir -p /tmp/systemd/RHBA-2020-3021-BE/
```
For PPC64LE, issue:
```
mkdir -p /tmp/systemd/RHBA-2020-3021-LE/
```

List all repositories and enable the repositories that are disabled, as required.

yum repolist all
yum-config-manager --enable rhel*

subscription-manager config --rhsm.manage_repos=1

Download the systemd update package.

For PPC64BE, issue:

yum update systemd*219-67.el7_7.10* --downloadonly –downloaddir=/tmp/systemd/RHBA-2020-3021-BE
yum update libgudev1-219-67.el7_7.10.ppc64.rpm --downloadonly –downloaddir=/tmp/systemd/RHBA-2020-3021-BE
yum update libgudev1-devel-219-67.el7_7.10.ppc64.rpm --downloadonly –downloaddir=/tmp/systemd/RHBA-2020-3021-BE

For PPC64LE, issue:

yum update systemd*219-67.el7_7.10* --downloadonly –downloaddir=/tmp/systemd/RHBA-2020-3021-LE
yum update libgudev1-219-67.el7_7.10.ppc64le.rpm --downloadonly –downloaddir=/tmp/systemd/RHBA-2020-3021-LE
yum update libgudev1-devel-219-67.el7_7.10.ppc64le.rpm --downloadonly –downloaddir=/tmp/systemd/RHBA-2020-3021-LE

The command-line kernel download method might fail if a newer kernel is available. In that case, use these steps.

Use one of the following steps depending on your platform:
- For PPC64BE, go to the following URL:
- For PPC64LE, go to the following URL:
Search for the required or any additional RPMs listed in About the ESS Red Hat Linux systemd update and download them.

Package the directory.
For PPC64BE, issue:
```
cd /tmp/systemd ; tar -zcvf systemd_ESS_5211_5361_BE.tgz RHBA-2020-3021-BE
```
For PPC64LE, issue:
```
cd /tmp/systemd ; tar -zcvf systemd_ESS_5211_5361_LE.tgz RHBA-2020-3021-LE
```
Note: Make sure that the RPM files are in the RHBA-2020-3021-BE or the RHBA-2020-3021-LE folder. Do not create any nested folder inside the RHBA-2020-3021-BE or the RHBA-2020-3021-LE folder and try to place the RPM file in that nested folder. Doing so results in failure of the systemd patch installation during the cluster deployment.
Disable the Red Hat Network connection on the management server node.
```
subscription-manager config --rhsm.manage_repos=0
yum clean all
```

Continue with the systemd update installation steps for systemd_ESS_5211_5361_BE.tgz or systemd_ESS_5211_5361_LE.tgz using gssdeploy -p. For example, use one of the following commands depending on the architecture to place the systemd update in the patch repository:

For PPC64BE, issue:

/var/tmp/gssdeploy -p systemd_ESS_5211_5361_BE.tgz.tar.gz –-silent

This command places the systemd updates in /install/gss/otherpkgs/rhels7/ppc64/patch

For PPC64LE, issue:

/var/tmp/gssdeploy -p systemd_ESS_5211_5361_LE.tgz –-silent

This command places the systemd updates in /install/gss/otherpkgs/rhels7/ppc64le/patch

For more information, see About the ESS Red Hat Linux systemd update.