When we retire an Orchestration service, the resulting stack will be retired. We do not force to retire VMs that belong to the stack. It is because other providers such as Amazon and Openstack, when a stack is deleted, all associated resources are automatically deleted together with the stack. However this is not the case for Azure, that only the stack (deployment) is deleted, leaving its associated resources untouched. As an RFE, we could add logic to force to delete associated resources to a stack, not limit only to VMs. There will be some issues concerning the stack retirement. We should have further discussions somewhere else.
https://github.com/ManageIQ/manageiq-providers-azure/pull/24
New commit detected on ManageIQ/manageiq-providers-azure/master: https://github.com/ManageIQ/manageiq-providers-azure/commit/71e9ea4a549450dda09c34a95a8911d566821046 commit 71e9ea4a549450dda09c34a95a8911d566821046 Author: Bill Wei <bilwei> AuthorDate: Mon Jan 16 09:12:55 2017 -0500 Commit: Bill Wei <bilwei> CommitDate: Mon Jan 16 09:26:24 2017 -0500 Delete all resources when deleting a stack https://bugzilla.redhat.com/show_bug.cgi?id=1393842 .../manageiq/providers/azure/cloud_manager/orchestration_stack.rb | 2 +- .../providers/azure/cloud_manager/orchestration_stack_spec.rb | 4 ++-- 2 files changed, 3 insertions(+), 3 deletions(-)
Merged to upstream
It's working now as of 5.8.0.10 Moving to verified.