Deployment not getting automatically deleted after decreasing the "Grace Period" of the lease.

Products

• VMware Aria Suite

Issue/Introduction

• Users may experience an issue where, after reducing the Grace Period for a Deployment's Lease, the Deployment is not automatically deleted or cleaned up when the new Grace Period expiry date is reached.

• For example:

  • If a user reduces the Grace Period for a Deployment's Lease from 90 days to 65 days, starting from 1st March 202#, the expected expiration date for the reduced Grace Period would be 5th May 202#. However, due to the issue, the Deployment is not automatically deleted or cleaned up on this date. Instead, it will expire based on the original 90-day Grace Period, which means the actual expiration date is 30th May 202#.

  • In this case, the issue causes the Deployment to follow the original 90-day Grace Period, resulting in an expiration date of 30th May 202# instead of the expected 5th May 202#.

     

Environment

• Aria Automation 8.18.1

Cause

• Known bug in Aria Automation 8.18.1.
• "lease_next_op_at" field is not reset when the Grace Period is lowered for a deployment Lease.

Resolution

• Raise a ticket with VMware by Broadcom Support to manually remove deployments which have exceeded the lowered Grace Period end date.
• Issue will be resolved in a version of VMware Cloud Foundation Automation 9.x.