Deployment objects enter a Missing state and Approvals fail

Products

• VMware Aria Suite

Issue/Introduction

If using an Approval policy with an Auto expiry trigger value set, projects which have been assigned to that policy must set the value for Request timeout on par with Auto expiry trigger of the Approval policy.

Symptoms:
Deployment objects enter a Missing state and Approvals fail

Environment

VMware vRealize Automation 8.6.x

Cause

Note: If no value is set for Request timeout within a Project's settings, the value defaults to 2 days.

If the below conditions are met, deployment objects will be deleted automatically by the system:

1. A Project's Request timeout value is less than an Approval policy's Auto expiry trigger value.
2. The act of approval is postponed more than the Request timeout value duration.

Resolution

This issue is resolved in vRealize Automation 8.8 and in the vRealize Automation Cloud April release.

Additional Information

Impact/Risks:

• Existing deployments will be unaffected by the corrective action to set the Request timeout value.

Note: These approvals will fail if they were initially misconfigured and meet the above Conditions defined in the Cause section of this article.

• New deployments should be initiated from the cloud templates of failed deployments that meet the above Conditions defined in the Cause section of this article after the corrective action on a Project's Request timeout value.
• This issue affects vRealize Automation 8.7 and below.

Note:  Please note this was considered normal product behavior in versions prior to 8.8.