Error: Invalid spaceKey on retrieving a related space config.

Viewing the status of a binary payload

After you create and deploy a binary payload, you can view the status in the AR System Single Point Deployment Status form.

To view the status of a binary payload

  1. On the AR System Administration console, open the AR System Single Point Deployment Payload form.
  2. Click Search and select a specific binary payload.
  3. Click the View Payload Status button.
    The AR System Single Point Deployment Status form opens and displays the detailed status for the selected binary payload along with the detailed status for each component that has the same deployment ID.


Binary payload deployment status values on the AR System Single Point Deployment Status form

The Status field on the AR System Single Point Deployment Status form shows the status of all the components in a payload. The following table lists the status values.

StatusDescription
Not ReadyWhen there is a dependent process, this status indicates that the dependent process is pending completion.
Pending DownloadIndicates binary payload download is pending.
DownloadingIndicates that the binary payload is downloading.
Download SuccessIndicates that the binary payload download is completed successfully.
Download FailedIndicates that the binary payload download is failed.
Deployment SuccessIndicates that the binary payload deployment is successfully completed.
Deployment FailedIndicates that the binary payload deployment is failed.
Pending RollbackIndicates that the rollback is pending for the binary payload.
Rollback SuccessIndicates that the binary payload rollback is successfully completed.
Rollback FailedIndicates that the binary payload rollback is failed.
SkippedIndicates that the binary payload deployment for a particular component was skipped because it is not applicable.
For example, a binary payload cannot be deployed on DSO.
User Cancelled

Indicates explicit cancellation of the binary payload on a specific server in a server group.

Timed Out

Indicates that the binary payload deployment timed out because the payload has remained in the same status for 48 hours, which is the default time-out criteria.

Monitor UnreachableIndicates that the BMC Remedy File Deployer process is stopped or is not working.

When a payload is deployed, the files are asynchronously deployed and each system might succeed or fail. If a file cannot be deployed to a specific system, the system automatically rolls back to the previously deployed version. In this case, you must correct the issues and Retry the deployment by using the Retry Deployment button on the AR System Single Point Deployment Status form.  

As a result, the status of a binary payload is different from the status displayed by BMC Remedy Deployment application.

The following table explains how rollback works when you create a binary payload using the AR System Single Point Deployment Payload form:

Status of a binary payload deploymentAction
Deployment failsThe Retry Deployment button on the  AR System Single Point Deployment Status form is enabled.
Deployment is successfulThe Retry Deployment button on the  AR System Single Point Deployment Status form is disabled.

When you click Start Rollback on the AR System Singe Point Deployment Payload form and

the binary payload deployment fails.

The Retry Deployment button on the  AR System Single Point Deployment Status form is enabled.

When you click Start Rollback on the AR System Singe Point Deployment Payload form and

the binary payload deployment is successfully rolled back.

The Retry Deployment button on the  AR System Single Point Deployment Status form is disabled.

Note

In AR System Deployment Management console, when a binary payload is successfully deployed, you can rollback the binary payload by using the Rollback button. If the binary payload deployment fails and you want to re-try, you must re-import or copy the package (binary payload) and deploy it.

Example: Understanding overall status of a binary payload

Consider you are deploying a binary payload in a server group with five servers. The following table shows the status of the binary payload on all five servers:

Server

1

Server

2

Server

3

Server

4

Server

5

Auto roll-backOverall payload status Description
NoneNoneNoneNoneNoneNonePendingStatus entry is not created.
Deployment successfulDownloadingNot ReadyNot ReadyNot ReadyNoneIn ProgressThe deployment has started.
Deployment successfulDeployment successfulDeployment successfulDeployment successfulDeployment successfulNoneSuccessfulThe deployment was successful on all the servers.
Deployment successfulDeployment successfulRollback SucccessfulRollback SucccessfulRollback SucccessfulNoFailedThe deployment was successful on two servers but failed on three servers.
Deployment successfulDeployment successfulRollback failedRollback failedRollback SucccessfulNoFailedThe deployment was successful on two servers but auto rolled back on two servers after failure.
Rollback SucccessfulPending RollbackDeployment successfulDeployment successfulDeployment successfulNoRollback in progressThe deployment has failed. Rollback is in progress.
Rollback SucccessfulRollback SucccessfulRollback SucccessfulRollback SucccessfulRollback SucccessfulNoRollback successfulThe rollback was successful.
Rollback SucccessfulRollback SucccessfulRollback failedRollback failedRollback SucccessfulNoRollback failedThe rollback is failed on two servers.
Deployment successfulDeployment successfulDeployment successfulDeployment successfulSkippedNoPartialsuccessThe deployment was successful on four servers but it was skipped on one server.
Deployment successfulDeployment successfulDeployment successfulUser cancelledUser cancelledNoPartial successUser Cancel was selected while the deployment was active on the third server.
Rollback successfulRollback successfulRollback successfulUser cancelledUser cancelledYesRollback successful

User cancel was selected while the rollback was active on the third server. The first three successful deployments wer rolled back.

SkippedSkippedSkippedSkippedSkippedNoneSkippedThere was no process to deploy or no path was found.
Deployment successfulDeployment successfulDeployment successfulDeployment successfulTimeoutNonePartial successThe deployment timed out because the status remained the same for more than 48 hours.
Deployment successfulDeployment successfulDeployment successfulWaiting for manual signalDeployment successfulNoneWaiting for manual signal

Since manual deployment was selected for the fourth server, the server waits for the adminstrator to run the arpayloadutil.bat or
arpayloadutil.sh file.

Note

In a server group environment with servers on multiple operating systems (for example Microsoft Windows and UNIX), the Microsoft Windows binary payload is successfully deployed on the Microsoft Windows server and the UNIX binary payload is successfully deployed on the UNIX server. However, because the Microsoft Windows binary payload gets skipped on the UNIX server and the UNIX binary payload gets skipped on the Microsoft Windows server, the overall payload status is displayed as Partial Success, even though the deployment is successful on that server.

Related topics

Creating and deploying a binary payload

Defining a custom binary payload

Was this page helpful? Yes No Submitting... Thank you

Comments