Is anyone aware of any known bugs with running gap-db commands? Running 'clear gap-db wired-mac c8:b5:ad:c6:6c:3e' doesn't appear to be removing the entry from the Conductor.
We have a few hundred APs which need removing from the Conductor GUI which do not seem to budge from running the command above. In theory would running 'ap gap-db re-initialize' remove these stale entries without having to go run a command per MAC address? These entries have been removed from the allowlist and are speaking to a different Conductor completely.
Software version: 8.10.0.5 - nothing in the release notes known issues.