Deployment issue /bin/bash^M: bad interpreter: No such file or directory

Products

• CA Identity Suite

Issue/Introduction

We faced deployment issue and found following errors from the ca_vapp_main log:

2024 Sep 27 13:01:23 testvapp InitSvc [ERROR] Initialization script for wildfly-idm exited with error status 126
2024 Sep 27 13:01:23 testvapp configureServices [ERROR] The service wildfly-idm failed to initialize (error code 126). Please inspect the log file: /opt/CA/VirtualAppliance/logs/ca_vapp_main.log
2024 Sep 27 13:01:23 testvapp initServices [ERROR] 126    Failed running services O/S configuration scripts on xx.xx.xx.xx: (error code: 126):
2024 Sep 27 13:01:23 testvapp initServices /opt/CA/VirtualAppliance/scripts/.firstrun/.CAVapp_functions: /opt/CA/.VAPP_install/wildfly-idm.sh: /bin/bash^M: bad interpreter: No such file or directory
2024 Sep 27 13:01:23 testvapp initServices [ERROR] Initialization script for wildfly-idm exited with error status 126
2024 Sep 27 13:01:23 testvapp initServices [ERROR] The service wildfly-idm failed to initialize (error code 126). Please inspect the log file: /opt/CA/VirtualAppliance/logs/ca_vapp_main.log
2024 Sep 27 13:01:23 testvapp updateMachineJson Entered function updateMachineJson with arguments: ERROR Fatal error: 126 
2024 Sep 27 13:01:23 testvapp deploySolution_main deploySolution terminated with exit code 126

Environment

Release : 14.4.2
Component : CA Identity Suite Virtual Appliance

Resolution

Engineering provided a fix (HF_VA-14.4.2-20241029140022-DE616968.tgz.gpg) to resolve this issue.

Additional Information

If you are experiencing the same issue, please create a support case and request the above fix.