OPERATIONAL DEFECT DATABASE
...
...
When the BIG-IP system fails to select a pool member, it provides an option to address the failure in an iRule. There are a few alternative commands to resolve the failure. These commands must be used separately. Combining them may result in connection reset or tmm restarts.
The BIG-IP system might reset the connection, generate two HTTP responses, or result in a tmm restart. Traffic disrupted while tmm restarts.
-- Virtual server has a configured iRule that includes both LB::reselect and HTTP::respond commands in the LB_FAILED event. -- The event LB_FAILED is fired for a connection.
There is no workaround other than not to use the HTTP::respond command after the LB::reselect command in the LB_FAILED event.
The BIG-IP system now generates an error during execution of HTTP::respond commands if an LB::reselect command was performed and reset a connection.
Click on a version to see all relevant bugs
F5 Integration
Learn more about where this data comes from
Bug Scrub Advisor
Streamline upgrades with automated vendor bug scrubs
BugZero Enterprise
Wish you caught this bug sooner? Get proactive today.
