I am running into a situation where the vApps I am deploying don't seem to be expiring and I am hoping somene can point me in the right direction. I suspect it has something to do with the value you set when deploying an individual vm as opposed to the vApp. In my workflow I first create a vApp which has no virtual machines. You have to specify the leas at that point in time. Let's say its 10 days from today ( april 3rd ). I then add however many vm's have been selected. Each vm gets deployed with vm.deploy(true,0,true) the 0 is supposed to be the runtime lease time in seconds (0 is no expire). After each vm has been deployed I then run System.getModule("com.vmware.library.vCloud.vApp").updateVAppLeaseSettings to set the lease time for the vApp. My thinking was this would be the final setting for the vApp Expiration. What I seem to have ended up with are vApps with an expiration date as I have specified but never expire. The date is perpetually being pushed out. So on the 5th of april that vApps expiration shows as april 15th. How is this possible after I have done a final set of the vApp's expiration? This may be my lack of knowledge with the vCD API but is there also a vm expiration? It is not exposed in the gui anywhere I have seen. Are the VM expirations which were set to no expiration trumping the vApp expiration? Did I miss a step after making the final vApp Lease setting?
Paul