Virtual systems deploy successfully with failed scripts
When you deploy a virtual system, failures with the associated deployment scripts can occur.
Symptoms
The deployment status of a virtual system might be displayed as completing successfully even though one or more non-critical scripts that are associated with the deployment fail to complete successfully.
Resolving the problem
Examine the History
section of the Virtual System Instance page to
ensure that associated scripts completed successfully during deployment.
- Click (or in 2.3.3.3 or later). If the instance was deployed from a classic virtual system pattern, click (or if in 2.3.3.3 or later).
- Click the instance name and view the History section.
Some script packages
that are defined to run at deployment time (by setting
"execmode":
0 in cbscript.json) are critical to
the success of a deployment, and can cause the deployment to fail
if the script does not complete successfully. There are a few scripts,
however, that do not result in a failed deployment if they fail during
deployment:- Must Gather Logs
- Default Add User
- Default Add NIC
- Default AIX add NIC
- WebSphere Application Server Hypervisor scripts
- Maestro scripts
Each script execution has an associated script status. After the script completed, the script status will have one of the following values:
Script statuses for virtual system patterns:
- RM05007
- Timeout.
- RM05008
- Failure.
- RM05009
- Warning.
- RM05010
- Success.
Script statuses for classic virtual system patterns:
- RM01000
- Waiting to execute.
- RM01006
- Started.
- RM01011
- Stopped.
- RM01012 - COMPLETE
- Completed successfully with a return code of 0.
- RM01013 - FAILED
- Completed with a return code other than 0 or 2, or did not get any result back from the virtual machine.
- RM01014 - FAILED
- Script could not be transferred to the virtual machine.
- RM01015 - FAILED
- Script did not complete before the timeout expired.
- RM01059 - WARNING
- Completed with a return code of 2.