In this situation the following conditions were met:
Running the following command on the controller provided us with more details on this issue:
- Successful ping between the controller and AP and vice versa
- Mint Link was successfully established between both
#show adoption pending
The AP was listed as pending adoption and the reason was due to a missing VX appliance license.
We confirmed this by running the following command:
Installing the VX appliance license resolved issue and allowed the AP to properly adopt and pull the config.
How to apply (add) any license key to a WiNG controller via the CLI
How to apply a WING VX appliance license key via the CLI