Bug ID 986761: If DCD addition to CM fails then rollback may also fail

Last Modified: May 03, 2021

Bug Tracker

Affected Product:  See more info
BIG-IQ AppIQ(all modules)

Known Affected Versions:
7.1.0,,,, 7.1.6,, 7.1.7,,, 7.1.8,,,,,, 7.1.9,,,, 8.0.0,

Opened: Jan 24, 2021
Severity: 3-Major


DCD rollback is not reflected in the UI following an unsuccessful addition of a DCD.


Zombie DCD will appear in the UI although the added DCD failed.


In some cases when a new DCD is added and an error occurred, DCD rollback may fail and DCD and will still appear in the UI. Attempting to remove the added DCD from the UI fails. This can occur when a DCD is added unsuccessfully. This may be an impact of system health issues,such as Elasticsearch connectivity problems, or Network health issues.


1. Get f5-rest-id of the managed dcd, run from dcd: # cat /config/f5-rest-device-id 2. Run from CM to manually to remove dcd from logging group: # curl -XPOST localhost:8100/shared/resolver/device-group-remover -d '{"deviceReference": {"link": "https://localhost/mgmt/shared/resolver/device-groups/cm-esmgmt-logging-group/devices/{f5-rest-deive-id}"}, "command":"DELETE_DEVICE_FROM_GROUP"}' 3. Run log to troubleshoot root cause of DCD add failure. 4. Add DCD after troubleshooting root cause is solved.

Fix Information


Behavior Change