Bug ID 1223589: Network Map page is unresponsive when a node name has the form "<IPv4>:<port>"

Last Modified: Mar 14, 2023

Bug Tracker

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

Known Affected Versions:
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, 15.1.4.1, 15.1.5, 15.1.5.1, 15.1.6, 15.1.6.1, 15.1.7, 15.1.8, 15.1.8.1, 16.1.0, 16.1.1, 16.1.2, 16.1.2.1, 16.1.2.2, 16.1.3, 16.1.3.1, 16.1.3.2, 16.1.3.3, 17.0.0, 17.0.0.1, 17.0.0.2

Opened: Jan 11, 2023
Severity: 4-Minor

Symptoms

The Network Map page does not load, the message "Loading..." continuously displayed on the page because the JavaScript throws an exception and does not terminate: Uncaught (in promise) TypeError: Cannot set properties of undefined (setting 'isNameHighlighted') at NetworkMapPresenter.clearHighlight (NetworkMapPresenter.js:1417:17) at NetworkMapPresenter.cardFilter (NetworkMapPresenter.js:1322:14) at Array.filter (<anonymous>) at NetworkMapPresenter.filterCards (NetworkMapPresenter.js:1315:51) at NetworkMapPresenter.filterSortAndGroupCards (NetworkMapPresenter.js:1306:10) at NetworkMapPresenter._callee18$ (NetworkMapPresenter.js:1162:14) at tryCatch (runtime.js:65:40) at Generator.invoke [as _invoke] (runtime.js:303:22) at prototype.<computed> [as next] (runtime.js:117:21) at step (fetch.js:461:47)

Impact

The Network Map loads all the virtual servers, pools, and nodes, but it throws an exception in the browser and the JavaScript never terminates, the message "Loading..." continuously displayed on the page and the page is unresponsive.

Conditions

- Node name should be of the form <IPv4:port>. - Node should be associated to a pool and then to a virtual server.

Workaround

Avoid naming a node as "<IPv4>:<port>".

Fix Information

None

Behavior Change