Kevin,
What version did you upgrade from? Did you follow the procedure to upgrade the backup partition on the RAP-5s prior to upgrading the code. From the release notes:
Upgrading With RAP-5 and RAP-5WN APs
If you have completed the first upgrade hop to the latest version of ArubaOS 5.0.4.x and your WLAN includes RAP-5/RAP-5WN APs, do not proceed until you complete the following process. Once complete, proceed to step 5 on page 79. Note that this procedure can only be completed using the controller’s command line interface.
1. Check the provisioning image version on your RAP-5/RAP-5WN Access Points by executing the show ap image versioncommand.
2. If the flash (Provisioning/Backup) image version string shows the letters rn, for example, 3.3.2.11-rn-3.0, note those AP names and IP addresses.
3. For each of the RAP-5/RAP-5WN APs noted in the step2, upgrade the provisioning image on the backup flash partition by executing the following command:
apflash ap-name <Name_of_RAP> backup-partition
The RAP-5/RAP-5WN reboots to complete the provisioning image upgrade.
4. When all the RAP-5/RAP-5WN APs with a 3.3.2.x-based RN provisioning image have successfully
upgraded, verify the provisioning image by executing the following command:
show ap image version
The flash (Provisioning/Backup) image version string should now show a version that does not contain the letters “rn”, for example, 5.0.4.8. If you omit the above process or fail to complete the flash (Provisioning/Backup) image upgrade to 5.0.4.x,
and the RAP-5/RAP-5WN was reset to factory defaults, the RAP will not be able to connect to a controller running ArubaOS 6.2.1.3 and upgrade its production software image