Environment:
UIM 20.33 with UIM Server, OC and CABI on their own robots.
CABI 4.20 with wasp 20.33HF2
Problem:
Followed Option 3 in knowledge Article ID 201551 - UIM 20.3 cabi deployment fails. - Keystore may have been tempered with which resolved the 'Keystore may have been tempered' error but now have a different install error where CABI probs fails to access the CABIJs url.
Error in cabi.log
[main, cabi] checking url=http://CABIIPADRESS:80/cabijs, timeAlreadyWaitedInSecs=350, maxTimeInSecs=600
nov 24 16:50:01:852 [main, cabi] connection.getResponseCode()=404
Release : 20.3
Component :
Incompatible wasp probe version with CABI
1. Restart the cabi robot and immediately deactivated the cabi probe before it reaches a failed state
2. Deploy cabi 4.30 over 4.20
3. Manually deployed the UIM Cabi packages below:
uim_cabi_availability_reports
uim_cabi_health_reports
uim_core_dashboards
uim_mcs_dashboards
uim_unified_reporter
uim_vmware_dashboards