Bug ID 741621: CLI preference 'suppress-warnings' setting may show incorrectly

Last Modified: Jun 10, 2021

Bug Tracker

Affected Product:  See more info
BIG-IP LTM(all modules)

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

Opened: Aug 24, 2018
Severity: 3-Major

Symptoms

At times when the 'suppress-warnings' setting is at its default value ('none'), it may be listed like this instead: suppress-warnings { } After loading the configuration, the 'suppress-warnings' setting may return to the default value, in which case it is no longer visible when listing out the CLI preferences (without specifying 'all-properties').

Impact

Possibly confusing listing for this value. The 'suppress-warnings' setting auto-populates with an incorrect default of empty { } (instead of 'none') on config load, causing it to be displayed when listing CLI preference in tmsh.

Conditions

-- Using the default value for 'suppress-warnings' in the CLI preferences. -- Listing out the CLI preferences.

Workaround

None

Fix Information

None

Behavior Change