I was adding a new AP3802I and it would not get IP from DHCP. Google search revealed the old Cisco bug (which may or may not be the case). However, log records were identical to this bug CSCvi14641.
I was able to resolve the issue after assigning a static IP to wired0 port using console connection, after that IP got on the network and everything started to work as expected. Hopefully someone can benefit from my finding and resolve this issue if they hit it in future.
Thank you for the response. WLC5508 running 188.8.131.52. Previously run 184.108.40.206 until 3 weeks ago or so. This AIR-AP3802I-B-K9 is the first that we provisioned using 220.127.116.11 (I think so). We have a mix of other AP3802(I/P) and they did not have such an issue, although some needed "dance around" with LAG support, if I recall correctly.
I don't have sufficient privileges to view the field notice
The FN is public facing and it is not secured behind a pay-wall. Anyone with a browser has full access to FN page. The Serial Number Validation Tool will require any CCO access -- The same CCO login used to post in this forum can be used to access the Serial Number Validation Tool.
NOTE: If the AP is indeed affected by this FN, take a screenshot of the result because it can/will be used to help speed up the RMA process.