AIR-CAP2602E join issues to WLC controller

So I bought a Cisco AIR-CAP2602E wireless access point about a month ago.  Currently we have an older 2506 controller and a newer 5500 controller sitting there un-used.

Since I did not have the time I had our telecom guy setup the base config on the 5500 and he spent a good 2-3 days trying to get this 2602 to see and join that controller to no avail.

I'll make a long story short.. I took this afternoon to play with it and checking out the console messages it was stuck in a loop:

*Mar 1 00:21:57.082: %CAPWAP-3-DHCP_RENEW: Could not discover WLC using DHCP IP. Renewing DHCP IP.
*Mar 1 00:22:00.105: %CAPWAP-3-ERRORLOG: Invalid event 38 & state 2 combination.
*Mar 1 00:22:00.208: %DHCP-6-ADDRESS_ASSIGN: Interface BVI1 assigned DHCP address 192.168.1.250, mask 255.255.255.0, hostname AP7081.0500.0000

Translating "CISCO-CAPWAP-CONTROLLER.example.com"...domain server (172.16.50.100)

*Mar 1 00:22:08.083: %CAPWAP-5-DHCP_OPTION_43: Controller address 172.16.50.25 obtained through DHCP
*Mar 1 00:22:08.083: %CAPWAP-3-ERRORLOG: Did not get log server settings from DHCP.
*Mar 1 00:22:08.173: %CAPWAP-3-ERRORLOG: Could Not resolve CISCO-CAPWAP-CONTROLLER.example.com
Not in Bound state.

(*ip's were changed to protect the innocent)

So it kept renewing is IP via DHCP but could not find the controller.  Now as far as I can tell, and what I found Googling the LAP's have to use DHCP.. which is fine.  And they can find the WLC in two ways:
DNS resolution by way of the CISCO-CAPWAP-CONTROLLER.domina.com or
DHCP Option 43


Option 43 takes a specific syntax all in Hex but here's the short of it:

It always begins with F1 then in my case I had two controller IP's so because of that the next piece is 08, the followed up with the ip's of my two controllers in hex.  So my string was:
F1080a0204120a020404

Now, admittedly while searching for help on the error "invalid event 38 & state 2 combination" I also came across a blog where the guy mentioned enabling the WLC to accept self-signed certs from the AP's.  So I did that as well... did not feel like testing the joining without that enabled so it *might* not be needed.

After setting the option 43 I bounced teh AP and it found and subsequently joined the controller.  WOOT.