vApp with runtime lease set to Never Expire is shutdown unexpectedly
search cancel

vApp with runtime lease set to Never Expire is shutdown unexpectedly

book

Article ID: 400823

calendar_today

Updated On:

Products

VMware Cloud Director

Issue/Introduction

  • vApp stopped on its own as it has exceeded its runtime lease
  •  vApp never had a defined runtime lease - it is set to "Never expire"
  • Following message can be seen in the vcloud-container-debug logs:

VAppCleanUpActivity            | [Activity Execution] Runtime lease has expired for [<vApp name> (########-####-####-####-############)] and power action suspend will be applied - Handle: urn:uuid:########-####-####-####-############, Current Phase: VAppCleanUpActivity$UnDeployExpiredVAppsPhase | activity=(com.vmware.ssdc.backend.VAppCleanUpActivity,urn:uuid:########-####-####-####-############)

Environment

VMware Cloud Director 10.6

Resolution

The runtime lease of vApp gets updated when a VM is imported into the vApp possibly from a backup solution.

The following KB Article can also be checked if there was a manual intervention: Alarm "Stopping vApp XXXX as it has exceeded its runtime lease" is received in Cloud Director