Last Modified: Jan 09, 2025
Affected Product(s):
BIG-IP APM, Install/Upgrade, LTM, TMOS
Known Affected Versions:
15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 15.1.1, 15.1.2, 15.1.2.1, 15.1.3, 15.1.3.1, 15.1.4, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 15.1.8.2, 15.1.9, 15.1.9.1, 15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5, 15.1.10.6, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 16.1.3.4, 16.1.3.5, 16.1.4, 16.1.4.1, 16.1.4.2, 16.1.4.3, 16.1.5, 16.1.5.1, 16.1.5.2, 17.0.0, 17.0.0.1, 17.0.0.2, 17.1.0, 17.1.0.1, 17.1.0.2, 17.1.0.3, 17.1.1, 17.1.1.1, 17.1.1.2, 17.1.1.3, 17.1.1.4, 17.1.2
Opened: Oct 15, 2024 Severity: 3-Major
Installing a BIG-IP Engineering Hotfix on a BIG-IP hardware platform may fail with the following message: "failed (RPM transaction failure.)" The /var/log/liveinstall.log file generated during the Engineering Hotfix may contain messages similar to the following: *** Live install start at 2024/10/08 19:38:23 *** ... info: RPM: apmclients-17.1.1.4-0.56.9.noarch info: RPM: error: unpacking of archive failed on file /usr/apm/images/apmclients-7247.2024.506.1332-6417.0.iso;67058ab9: cpio: write info: RPM: error: apmclients-17.1.1.4-0.56.9.noarch: install failed ... Terminal error: RPM transaction failure. *** Live install end at 2024/10/08 19:41:26: failed (return code 2) *** This problem occurs because the apmclients and epsec RPM packages install their contents to the /usr/apm/images directory, which fails if there is insufficient space in the /usr volume for the temporary files created during RPM package installation.
The affected BIG-IP Engineering Hotfix cannot be installed on the affected platform.
This may occur under the following conditions: -- Installing a BIG-IP Engineering Hotfix on a BIG-IP hardware platform which lacks sufficient available storage space (less than approximately 100MiB) in the /usr volume. Check available space in /usr with the following command: df -h /usr (NOTE: It is theoretically possible for this issue to occur when installing Engineering Hotfix in a BIG-IP VE instance, but the BIG-IP software does not consume as much space on the /usr volume when installed to a VE instance. Various additional components that are required for BIG-IP to run on F5 hardware platforms are not required for VE instances.) -- The BIG-IP Engineering Hotfix contains an updated "apmclients" and/or "epsec" package. This can be confirmed by issuing the following command (at a bash prompt) against the BIG-IP Engineering Hotfix ISO file: isoinfo -Rf -i /shared/images/Hotfix-BIGP-<version>.<EngHF#.build>-ENG.iso | grep -e apmclients -e epsec
To work around this issue: 1. Install the BIG-IP Release version to the desired volume set (e.g., HD1.3). For example: -- from a bash command prompt: tmsh install sys software image BIGIP-17.1.1.4-0.0.9.iso volume HD1.3 -- from a tmsh command prompt: install /sys software image BIGIP-17.1.1.4-0.0.9.iso volume HD1.3 2. Increase the size of /var volume in the target volume set (e.g., HD1.3). For example, from a bash command prompt: lvextend -L+500M --resizefs /dev/mapper/vg--db--sda-set.3._usr 3. Install the BIG-IP Engineering Hotfix to the target volume set (e.g., HD1.3). For example: -- from a bash command prompt: tmsh install sys software hotfix Hotfix-BIGIP-17.1.1.4.0.56.9-ENG.iso volume HD1.3 -- from a tmsh command prompt: install /sys software hotfix Hotfix-BIGIP-17.1.1.4.0.56.9-ENG.iso volume HD1.3
None
/usr mount point size requirement increased over time, extended the size of each installed volume increased by 500MB by increasing /usr size. As the system is not increasing the disk size but only increasing allocation at /usr, the available disk space for other consumption will be impacted accordingly and you need to adjust accordingly.