Last Modified: Apr 12, 2021
See more info
Known Affected Versions:
14.1.0, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 14.1.2, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206, 220.127.116.11, 18.104.22.168, 15.0.0, 15.0.1, 22.214.171.124, 126.96.36.199, 188.8.131.52, 184.108.40.206
Opened: Jul 18, 2019
Installation of an Engineering Hotfix based on BIG-IP 14.1.0 or later may fail in some cases if the Engineering Hotfix contains an updated nash-initrd package. When this issue occurs: -- The system software status for the affected volume on the new blade shows a status of 'failed (RPM transaction failure.)' -- The /var/log/liveinstall.log file on the new blade contains a message similar to the following: info: RPM: error: %post(nash-initrd-220.127.116.11-68.el18.104.22.168.7.x86_64) scriptlet failed, exit status 1.
Unable to install a software image containing an affected Engineering Hotfix to one or more blades in VIPRION chassis.
This issue may occur under some conditions when installing an Engineering Hotfix based between BIG-IP 14.1.0 and 22.214.171.124 inclusive, which contains an updated nash-initrd package. The specific conditions under which this issue may occur have not been confirmed, but are reported to include: -- Using B4450, B2100, B2150 or B2250 blades in a VIPRION chassis. -- Installing an affected Engineering Hotfix into a new software volume on all blades in the chassis. -- Inserting a new blade into a VIPRION chassis where the primary blade is running an affected Engineering Hotfix but the new blade is currently running an older BIG-IP software version (such as v12.1.x). There may be other conditions under which this problem may occur which have not yet been confirmed. See Bug Tracker for updated information as details are confirmed.
Specific workarounds for specific reported conditions have not yet been confirmed, but may include: -- In a VIPRION chassis, booting into a software volume that is not running an affected Engineering Hotfix; inserting the new blade and waiting for all software volumes to be successfully installed/updated; and then booting the blades into the software volume that is running the affected Engineering Hotfix. -- In a VIPRION chassis, rebooting all blades into a common volume that has been successfully installed (such as v12.1.x); waiting for the failed software installation to be automatically retried; and then rebooting the blades into the software volume that is running the affected Engineering Hotfix. -- Temporarily installing a new blade into a separate VIPRION chassis with no other blades; manually reinstalling the affected Engineering Hotfix into the affected volume; and then installing the new blade into the existing chassis. -- In a VIPRION chassis, installing the Release image on which the desired Engineering Hotfix is based into a new volume; booting into the new volume; rebooting into the original volume; installing the Engineering Hotfix into the new volume; and then booting into the new volume. There may be other workarounds which are effective in avoiding and/or resolving this issue under specific conditions but have not yet been confirmed. See Bug Tracker for updated information as details are confirmed.
A software image containing an Engineering Hotfix which includes an updated nash-initrd package may be successfully installed into blades in VIPRION chassis.