Last Modified: May 29, 2024
Affected Product(s):
BIG-IP Install/Upgrade, TMOS
Known Affected Versions:
13.1.0, 13.1.0.1, 13.1.0.2, 13.1.0.3, 13.1.0.4, 13.1.0.5, 13.1.0.6, 13.1.0.7, 13.1.0.8, 13.1.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 13.1.3, 13.1.3.1, 13.1.3.2, 13.1.3.3, 13.1.3.4, 13.1.3.5, 13.1.3.6, 13.1.4, 13.1.4.1, 13.1.5, 13.1.5.1, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.0.1, 14.0.1.1, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.5, 14.1.0.6, 14.1.2, 14.1.2.1, 14.1.2.2, 14.1.2.3, 14.1.2.4, 14.1.2.5, 14.1.2.6, 14.1.2.7, 15.0.0, 15.0.1, 15.0.1.1, 15.0.1.2, 15.0.1.3, 15.0.1.4, 15.1.0, 15.1.0.1, 15.1.0.2, 15.1.0.3, 15.1.0.4, 15.1.0.5, 16.0.0, 16.0.0.1
Fixed In:
16.1.0, 16.0.1, 15.1.1, 14.1.2.8
Opened: Jan 21, 2020 Severity: 2-Critical Related Article:
K40370152
Software upgrades to an Engineering Hotfix on a vCMP guest might fail with one of the following messages: failed (Software compatibility tests failed.) failed (The requested product/version/build is not in the media.) The failed installation is also indicated by log messages in /var/log/ltm similar to: -- info lind[5500]: 013c0007:6: Install complete for volume=HD1.2: status=failed (Software compatibility tests failed.) -- info lind[5500]: 013c0007:6: Install complete for volume=HD1.2: status=failed (The requested product/version/build is not in the media.)
Unable to perform software installations on vCMP guests using installation media located on the vCMP host.
This may occur when performing a software upgrade to an engineering hotfix on a vCMP guest running affected versions of BIG-IP software, when the software images are present on the vCMP host. This can be accomplished by running the following command from the vCMP guest console: tmsh install sys software block-device-hotfix <hotfix-image-name> volume <volume.name>
Option 1: =========== Make sure that the .iso files for both base image and engineering hotfix are copied to the vCMP guest (under /shared/images) before starting the installation. If installing the software from the command line, use syntax similar to the following: tmsh install sys software hotfix <hotfix-image-name> volume <volume.name> Option 2: =========== Even if the engineering hotfix installation has failed, the base image should still have been installed properly. You can restart the vCMP guest and perform a hotfix installation on top of already installed base image, using syntax similar to the following: tmsh install sys software hotfix <hotfix-image-name> volume <volume.name> Option 3: =========== Even if the engineering hotfix installation has failed, the base image should still have been installed properly. Ensure there is copy of the engineering hotfix image locally within the vCMP Guest. Then restart the lind service on the vCMP Guest: tmsh restart sys service lind If running the vCMP Guest on multiple slots, you may need to restart lind on all slots. From the primary slot on the vCMP Guest, run: clsh tmsh restart sys service lind The hotfix installation should begin again, this time using the hotfix from within the /shared/images/ location on the vCMP Guest. Option 4: =========== Manually eject the CD from the vCMP guest's virtual CD drive, and then restart lind. On the vCMP Guest: 1. Confirm the wrong ISO image is still locked (inserted in the CD drive): isoinfo -d -i /dev/cdrom Note: Pay attention to the volume ID in the output from within the vCMP guest. 2. Unlock (eject) the image: eject -r -F /dev/cdrom && vcmphc_tool -e 3. Verify the CD drive is now empty: isoinfo -d -i /dev/cdrom The output should report an error that includes: <...> Sense Code: 0x3A Qual 0x00 (medium not present) Fru 0x0 <…> 4. Restart lind: tmsh restart sys service lind If running the vCMP Guest on multiple slots, you may need to restart lind on all vCMP Guest slots. From the primary slot on the vCMP Guest, run: clsh tmsh restart sys service lind
Software upgrades on a vCMP guest complete successfully even when the software images are present on the vCMP hypervisor.