Bug ID 716915: Changing iRule attached to IVS can cause 'not ready for connections' error

Last Modified: Nov 22, 2021

Bug Tracker

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

Known Affected Versions:
14.0.0, 13.1.0, 13.0.1, 13.0.0

Opened: Apr 25, 2018
Severity: 3-Major

Symptoms

Internally connecting from a parent virtual server to an internal virtual server (IVS) fails, resulting in failure of whatever service was being attempted. This is indicated by the following error message: err tmm1[29909]: 017b0002:3: IVS (connection from parent 172.16.88.20:60109 -> 10.10.10.10:80): Internal virtual server /Common/ivs_name is not ready for connections. Subsequent transactions on the IVS on the same TMM fail.

Impact

The transaction in progress succeeds, but the next transaction on the IVS on the same TMM fails, along with the service it was part of. The IVS no longer functions on the affected TMM until the TMM is restarted.

Conditions

A transaction on a virtual server is in the process of connecting to the IVS internally, while at the same time an iRule is added or modified on that IVS. Note: This issue occurs because of a race-condition, so it occurs intermittently.

Workaround

There is no workaround other than not changing iRules on an IVS while a transaction on a virtual server is in the process of connecting to the IVS internally. If this occurs after changing the configuration, restart the TMM. Traffic disrupted while TMM restarts.

Fix Information

None

Behavior Change