8.1.4.2 Installing the Fix Pack icp-3.2.1.2203-build601095-48411
There are two fix pack versions available, 3.2.1.x fix packs and 3.2.2.x fix packs. The 3.2.1.x fix packs are intended for environments that include Kubernetes version 1.13.12. See:
https://www.ibm.com/docs/en/cloud-private/3.2.x?topic=support-fixed-reported-problems#fixpack_2203
Note: If you apply a 3.2.2.x fix pack, do not apply an equivalent 3.2.1.x fix pack.
The Fix Pack is downloaded as shown in Figure 8.17 earlier and the Download Director applet displays each of the installation files of the Fix Pack set. The install file we need is as shown and highlighted in Figure 8.24:
Figure 8.24: The Fix pack file we need is highlighted and is around 16.7 GBytes (17918675533 bytes)
On completion, which took around 3.5 hours, we have the full download as shown in Figure 8.25:
Figure 8.25: The Fix pack file ibm-cloud-private-x86_64-3.2.1.2203.tar.gz size 16.7 GBytes downloaded
Copy the ibm-cloud-private-x86_64-3.2.1.2203.tar.gz file downloaded as shown in Figure 8.26:
Figure 8.26: The Fix pack file, ibm-cloud-private-x86_64-3.2.1.2203.tar.gz is copied to the InstallFP2203 installs sub-folder
cd /opt/
mkdir installFP2203
cd /opt/installFP2203
cp /mnt/hgfs/IBMCloudPrivate/IBM_Cloud_Private3.2.1.2203/ibm-cloud-private-x86_64-3.2.1.2203.tar.gz .
Extract the images from the fix pack and load the images into Docker. Remove the old base install file to give some additional disk space as shown in Figure 8.27:
rm -rf /opt/ibm-cloud-private-3.2.0/cluster/images/ibm-cloud-private-x86_64-3.2.1.tar.gz
tar xf ibm-cloud-private-x86_64-3.2.1.2203.tar.gz -O | docker load
Figure 8.27: The old base install file is removed to give some additional disk space
The first run we get the error shown in Figure 8.28:
Figure 8.28: The “no space left on device” error is displayed during the docker load
Error processing tar file(exit status 1): write /usr/local/helm/linux-amd64/helm: no space left on device
So, we need to check how much space can be reclaimed due to unused images. The docker system df shows the RECLAIMABLE space available, in Figure 8.29:
Figure 8.29: The docker system df command shows nearly 100 GBytes of reclaimable disk space
If RECLAIMABLE amount is greater than zero (which is definitely the case) then we can run the command:
docker system prune -a
This command will clean up all the unused space as shown in Figure 8.30:
Figure 8.30: The docker system prune -a command will clean up all the unused space
This command will clean up:
• All stopped containers
• All networks not used by at least one container
• All images without at least one container associated to them
• All build caches
The list of images to be deleted is displayed as shown in Figure 8.31:
Figure 8.31: The list of images to be deleted is displayed
The Total reclaimed space is shown as 102.5 GBytes in Figure 8.32.
Figure 8.32: The Total reclaimed space was 102.5 GBytes
The docker ps and docker system df commands now show the recovered disk space and current container usage as illustrated in Figure 8.33:
Figure 8.33: The docker ps and docker system df commands now show the recovered disk space
The docker command can now be repeated (if the lack of space requires the above remediation):
tar xf ibm-cloud-private-x86_64-3.2.1.2203.tar.gz -O | docker load
The above command is used to load the IBM Cloud Private 3.2.1 container as shown in Figure 8.34:
Figure 8.34: The highlighted command is used to load the IBM Cloud Private 3.2.1 container
The Fix Pack image is loaded as docker container images as shown in Figure 8.35.
Figure 8.35: The Fix Pack image is now loaded without error, ready for installation
Move the fix pack file to the cluster//cluster/images folder:
mv /opt/installFP2203/ibm-cloud-private-x86_64-3.2.1.2203.tar.gz /opt/ibm-cloud-private-3.2.0/cluster/images
cd /opt/ibm-cloud-private-3.2.0/cluster
Apply the fix pack images to the cluster:
cd /opt/ibm-cloud-private-3.2.0/cluster
docker run -e LICENSE=accept –net=host –rm -t -v
“
$(pwd)
“
:/installer/cluster \
ibmcom/icp-inception-amd64:3.2.1.2203-ee apply-fixpack
Now we get the following error, so:
start:
‘
2022-12-04 12:09:29.455386
‘
stderr: /tmp and /var/lib/docker directories total available disk space 104 GB, it should be greater than or equal to 119 GB
Stop any running containers (docker ps gives the Container IDs):
(base) [root@ecmukdemo10 opt]# docker stop d98dad31b77c
d98dad31b77c
(base) [root@ecmukdemo10 opt]# docker stop 92705574df8c
92705574df8c
(base) [root@ecmukdemo10 opt]# docker stop a73ee96ff4d8
a73ee96ff4d8
(base) [root@ecmukdemo10 opt]# docker stop ddad9d71a503
Removed install sets:
rm -rf DATA_STUDIO_CLIENT_V4.1.3_FOR_LIN.tar.gz
cd /opt/installs/DataStudio4.1.3/disk1
rm -rf -R *
cd /opt/Workplace4-0-2
rm -rf -R *
cd /root/Downloads
rm -rf .zip cd /tmp rm -rf -R vm
cd /opt/IBM/cloudpak4data
rm -rf cloudpak4data-ste-3.0.1.tgz
cd /opt/IBM/DS4.1.3
rm -rf -R *.tar.gz
cd /tmp
rm -rf -R *
cd /home/wasadm/Downloads
rm -rf *.gz
rm -rf *.tgz
Note: The install requires a working Firewall.
Using the command: firewall-cmd –reload
If this gives the following:
Traceback (most recent call last):
File
“
/usr/bin/firewall-cmd
“
, line 31, in
from firewall.client import FirewallClient, FirewallClientIPSetSettings, \
File
“
/usr/lib/python3.6/site-packages/firewall/client.py
“
, line 29, in
import slip.dbus
File
“
/usr/lib/python3.6/site-packages/slip/dbus/init.py
“
, line 8, in
from .
import service
File
“
/usr/lib/python3.6/site-packages/slip/dbus/service.py
“
, line 30, in
from six import with_metaclass
ModuleNotFoundError: No module named ‘six’
The solution to fix this is just to copy the six.py file as follows:
cp /usr/local/lib/python3.6/site-packages/six.py /usr/lib/python3.6/site-packages/
This allows the commands to be run as follows:
systemctl start firewalld
firewall-cmd –reload
success
Rerun the fix pack images to the cluster after releasing to 130 GBytes free:
cd /opt/ibm-cloud-private-3.2.0/cluster
docker run -e LICENSE=accept –net=host –rm -t -v
“
$(pwd)
“
:/installer/cluster \
ibmcom/icp-inception-amd64:3.2.1.2203-ee apply-fixpack
Restart the IBM FileNet Cloud Private Container Images:
docker start d98dad31b77c
docker start 92705574df8c
docker start a73ee96ff4d8
docker start ddad9d71a503
