Symptoms

Instant deployments (i.e., updating the BIG-IP state of a virtual server or pool member outside of the Change Management module) within a manually-synced, clustered BIG-IP environment will result in an error being thrown for one of the two BIG-IPs. Furthermore, the two BIG-IPs will be in Changes Pending state following the deployment.

Impact

The deployment will fail to one of the two devices, and the BIG-IP devices will be left in Changes Pending state.

Conditions

BIG-IP cluster is setup as a manually-synced cluster (Sync-Failover group is set to Manual Sync).

Workaround

Log into one of the BIG-IP devices, and manually sync the changes from the one device that got the change to the other one (Click the "Changes Pending" link in the top-left corner). Or setting the cluster to automatically sync. Alternatively, the cluster can be sync'd via the BIG-IQ UI using the Device Management -> DSC Groups and syncing in the DSC Group Properties.

Fix Information

None

Guides & references

K10134038: F5 Bug Tracker Filter Names and Tips