Bug ID 929213: iAppLX packages not rolled forward after BIG-IP upgrade

Last Modified: Feb 01, 2023

Bug Tracker

Affected Product:  See more info
BIG-IP Install/Upgrade, TMOS(all modules)

Known Affected Versions:
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, 14.1.2.8, 14.1.3, 14.1.3.1, 14.1.4, 14.1.4.1, 14.1.4.2, 14.1.4.3, 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, 16.1.0, 16.1.1

Fixed In:
17.0.0, 16.1.2, 15.1.4.1, 14.1.4.4

Opened: Jul 21, 2020
Severity: 3-Major

Symptoms

Certain iAppLX packages are not rolled forward after a BIG-IP upgrade or restoring a UCS file generated from an affected system, and will be unavailable for use. 1. f5-cloud-failover-1.4.0-0.noarch.rpm 2. f5-service-discovery-1.2.9-2.noarch.rpm 3. f5-telemetry-1.12.0-3.noarch.rpm

Impact

After upgrading or restoring a UCS file generated from an affected system, the cloud-failover, service discovery, and telemetry iAppLX apps are not available for use, and will result in 404 error, while accessing them from GUI

Conditions

-> Installing any of the below iAppLX packages 1. f5-cloud-failover-1.4.0-0.noarch.rpm 2. f5-service-discovery-1.2.9-2.noarch.rpm 3. f5-telemetry-1.12.0-3.noarch.rpm -> Performing an upgrade -> Trying to access the LX packages from GUI by navigating to iApps -> Package Management LX

Workaround

The package needs to be uninstalled and installed again for use. Steps: -> From GUI, Navigate to iApps -> Package Management LX -> select the package to uninstall and click on Uninstall -> click on Import and provide the path of package to install again

Fix Information

A new database key has been added, 'sys db iapplxrpm.timeout', which allows the RPM build timeout value to be increased. sys db iapplxrpm.timeout { default-value "60" scf-config "true" value "60" value-range "integer min:30 max:600" } For example: tmsh modify sys db iapplxrpm.timeout value 300 tmsh restart sys service restjavad Increasing the db key and restarting restjavad should not be traffic impacting. After increasing the timeout, the RPM build process that runs during a UCS save should be successful, and the resulting UCS should include the iAppsLX packages as expected. Note: The maximum db key value of 600 may be needed in some cases.

Behavior Change