servicecatalog
"VMWare controller:" In error cases the controller does not automatically cleanup
[Version] V16.0 Fix 6 [Date] 2016/07/13
[Test category] Creative
[Description] In error cases the controller does not automatically cleanup once a instantiation of an vmware image goes wrong. [Steps to reproduce] Any situation where a deployment goes wrong. [Expected result] Info (error) email is sent to responsible persons; no error is given on the CT-MG UI; Subscription is automatically terminated; Service instance is deleted from VMWare controller, VMWare instance on ESS is removed.
[Observed result] Info (error) email is sent to responsible persons; Subscription remains in status "pending"; Service instance is 'static' on VMWare controller (timer is inactive); VMWare instance on ESS exists, but is (un)accessible from CT-MG.
[Details] See above;
[Messages and logs]
The impact of this issue is the need for manual intervention of the administrator, who is operating the APP environment of the VMware controller. It's resulting from a non unique error handling. That's sure an inconvenience for administrators. But it's not major. A workaround exists and the occurrence is limited to exceptional cases where provisioning fails.
Let's tackle this with the August release.
Some VMWare contorller issues are already solved from contributors. Check if the problem still exist, after the last contribution will be finished.
