EDIT- I have asked for Jason's notes as I haven't seen this before nor was I notified. I am going to look in to the bugs noted, etc in the release notes to see if this is the same issue as Jason found. Sorry for the trouble. Am leaving the below intact in case it applies to you, or someone else...
########
That is likely not the issue. You would need to get into the console of the mesh point to find out for sure, is that something you can do?
If a point comes up under 'open' but NOT as WPA2-PSK, that usually means that the MeshRecovery profile doesn't match, and that either the mesh point was provisioned on a different controller than the portal is on, *OR* the controller has since been replaced from when the AP was first deployed and the mesh point wasn't re-provisioned.
The only fix is to either do one of two things:
1. pull the mesh point down, bring it onto the LAN, purge, reprovision as a mesh point, and return to the pole.
2. Find a spare controller, make it a local of your master controller (so that it gets the required meshrecovery profile), then take the controller out to the AP, configure a DHCP scope on the local controller out at the pole, console in to the AP-175, purge, let it come up on your local with a DHCP so that the AP will find the local, provision the Mesh point into the correct group, disconnect and reboot the mesh point and watch it come up in the console to make sure it works, then check on the controller on the LAN.
Let me know if any of the above conditions ring a bell in regards to how the point was deployed or if the controller has since been replaced from when the AP mesh point was first deployed.