Troubleshooting Application Installation Job issues

Application software installation begins after the user creation job completes successfully. To install applications on a physical or virtual guest, you must create an Application Component Template (ACT) in BMC Server Automation.

The ACT resides in the /Component Templates/CSM_Application_Packages folder in BMC Server Automation. The component template must define the installation Batch Job specified in the Install / Uninstall tab of the ACT. Any application software (ACTs) added to the service blueprint or added via options while submitting the service offering instance (SOI) are executed after the user creation job completes successfully. The ACTs specified via options are appended to the list of ACTs in the service blueprint. The ACTs added to service blueprint are installed before installing ACTs that are driven via options.

To understand what is happening behind the scenes, BMC Cloud Lifecycle Management gets an updated blueprint json file that has the entries appended as options. The ACTs trigger the parent Batch jobs in BMC Server Automation, which in turn trigger the Deploy jobs or any other BMC Server Automation jobs that are added to the Batch job. For information on adding ACTs to BMC Cloud Lifecycle Management, see knowledge article 000093287.

Troubleshooting

Check the individual job logs from BMC Server Automation for errors. If the application installation takes a long time, BMC Cloud Lifecycle Management may mark the job as complete and fail the SOI.

Below, the entries from csm.log indicate that the Platform Manager polls the status of the Batch job on BMC Server Automation ten times and then marks the job as complete even before the job was actually completed by BMC Server Automation.

07 Sep 2011 13:00:55,614 [INFO] API - [Thread=0acc35b0-52fa-4ac9-9509-6af7a5a46557::67756fdc-55fb-46a1-b2f3-f552df421f00(348)] [Class=BaseBBSATaskExecHelper:pollForCompletion] - Retrieving BBSA job status. Poll count: 10. Status URI = /id/SystemObject/Job/Batch Job/6a5ae36d-fbeb-404d-8212-43c147970801/Statuses/Schedule2027301
07 Sep 2011 13:00:55,928 [INFO] API - [Thread=0acc35b0-52fa-4ac9-9509-6af7a5a46557::67756fdc-55fb-46a1-b2f3-f552df421f00(348)] [Class=BaseBBSATaskExecHelper:pollForCompletion] - BBSA Job is not complete. Waiting to poll for BBSA job status for /id/SystemObject/Job/Batch Job/6a5ae36d-fbeb-404d-8212-43c147970801/Statuses/Schedule2027301
07 Sep 2011 13:00:59,036 [ERROR] API - [Thread=0acc35b0-52fa-4ac9-9509-6af7a5a46557::a255806d-c6c0-4191-8b0e-916fcbb122cf(341)] [Class=ApplicationSoftwareCreateExecHelper:execute] - Application Software: creation failed.
07 Sep 2011 13:00:59,036 [INFO] API - [Thread=0acc35b0-52fa-4ac9-9509-6af7a5a46557::a255806d-c6c0-4191-8b0e-916fcbb122cf(341)] [Class=ApplicationSoftwareCreateExecHelper:execute] - Completed installing application software on server: was25-3

Because the Batch job was still running after ten status polls, BMC Cloud Lifecycle Management considers the job to have failed and completes the application software installation task.

Two properties in the providers.json file control how BMC Server Automation conducts software job status polling.

• BBSA_SOFTWARE_JOB_STATUS_POLL_INTERVAL_SECONDS
  Default Value - 60
• BBSA_SOFTWARE_JOB_STATUS_POLLS
  Default Value - 10

Increase the value of the property BBSA_SOFTWARE_JOB_STATUS_POLLS to provide more time for BMC Server Automation to complete the Batch job.