Bug ID 793669: FQDN ephemeral pool members on HA pair doesn't get properly synced of the new session value

Last Modified: Jul 16, 2019

Bug Tracker

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

Known Affected Versions:
12.1.0, 12.1.0 HF1, 12.1.0 HF2, 12.1.1, 12.1.1 HF1, 12.1.1 HF2, 12.1.2, 12.1.2 HF1, 12.1.2 HF2, 12.1.3, 12.1.3.1, 12.1.3.2, 12.1.3.3, 12.1.3.4, 12.1.3.5, 12.1.3.6, 12.1.3.7, 12.1.4, 12.1.4.1, 13.0.0, 13.0.0 HF1, 13.0.0 HF2, 13.0.0 HF3, 13.0.1, 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.1, 13.1.1.2, 13.1.1.3, 13.1.1.4, 13.1.1.5, 14.0.0, 14.0.0.1, 14.0.0.2, 14.0.0.3, 14.0.0.4, 14.0.0.5, 14.1.0, 14.1.0.1, 14.1.0.2, 14.1.0.3, 14.1.0.4, 14.1.0.5, 14.1.0.6, 15.0.0

Opened: Jun 14, 2019
Severity: 3-Major

Symptoms

On a high availability (HA) paired device group configuration, where there are FQDN nodes as pool members in a pool, when the pool member is enabled or disabled on one device, and with config-sync, the other device does not fully update the peer. The template node gets updated with the new value, but the ephemeral pool member retains the old value.

Impact

FQDN pool member enabling/disabling is not being fully propagated to the other device after config-sync.

Conditions

Steps to Reproduce: 1. Configure HA, specifically a Device group (e.g., Failover) with two BIG-IP systems. 2. Create an HTTP pool (TEST_FQDN_POOL) and FQDN Pool Member on both systems. 3. Wait for the FQDN pool member to report as AVAIL_GREEN and the ephemeral node as AVAIL_BLUE on both systems. 4. Tmsh login to any of the systems. 5. Run the command: tmsh run cm config-sync to-group Failover 6. Run the command: tmsh modify ltm pool TEST_FQDN_POOL members modify { example.com:http { session user-disabled } } 7. Run the command: tmsh run cm config-sync force-full-load-push to-group Failover

Workaround

None.

Fix Information

None

Behavior Change