Bug ID 1349933: GUI "Install Configuration" option shows wrong options when a software volume has 15.1.10 installed

Last Modified: Sep 24, 2024

Affected Product(s):
BIG-IP Install/Upgrade, TMOS(all modules)

Known Affected Versions:
15.1.10, 15.1.10.2, 15.1.10.3, 15.1.10.4, 15.1.10.5

Opened: Sep 08, 2023

Severity: 3-Major

Symptoms

When using the GUI to switch boot locations to BIG-IP 15.1.0 or a later release in the 15.1.x branch of software from a previous 15.1.x software version, the "Install Configuration" option may not work properly, and may either: - show a blank list of source boot volumes - show an incomplete or incorrect list of source boot volumes Source boot locations running any software version between BIG-IP 15.1.1 and BIG-IP 15.1.9.1 will not be listed. If the "Source Volume" field is left blank, pressing "Activate" will cause the system to report the error "null does not exist." Similarly, when switching to a boot location running BIG-IP 15.1.1 through BIG-IP 15.1.9.1, the GUI will incorrectly list a 15.1.10 boot location as a valid source for installing the configuration. Configuration cannot be backported, so the system should not indicate this is valid.

Impact

The "Install Configuration" option does not show the correct set of source volumes for copying configuration to a target boot location.

Conditions

Attempting to activate a boot location running BIG-IP 15.1.10 or later in the BIG-IP v15.1.x branch of software.

Workaround

By default, the software installation process copies the configuration to the new boot location during the install, as described in K13438: Controlling configuration import when performing software upgrade/installation (https://my.f5.com/manage/s/article/K13438). If that is the case and no changes have been made since that installation was performed, it may not be necessary to install configuration when changing boot locations, and the "Install Configuration" option can be set to "No". If the administrator does still want to copy the configuration prior to activating the new boot location, use the "cpcfg" utility from the command-line, as described in K14724: Using the cpcfg command to copy a configuration from one boot location to another (https://my.f5.com/manage/s/article/K14724)

Fix Information

None

Behavior Change

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips