https://github.com/ManageIQ/manageiq/pull/13548

New commit detected on ManageIQ/manageiq/euwe:
https://github.com/ManageIQ/manageiq/commit/3c8aba3c7449bf4158cf3c27b2e8ada35d80134c

commit 3c8aba3c7449bf4158cf3c27b2e8ada35d80134c
Author:     Bill Wei <bilwei@redhat.com>
AuthorDate: Tue Jan 17 15:39:27 2017 -0500
Commit:     Bill Wei <bilwei@redhat.com>
CommitDate: Tue Jan 17 16:27:59 2017 -0500

    Accept option to delete all resources together with a stack
    
    Upstream commit 71e9ea4a549450dda09c34a95a8911d566821046
    
    There is a difference from the upstream where by default all resources are deleted
    with the stack. For Euwe we will only delete resources when the flag is on.
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1414003

 .../manageiq/providers/azure/cloud_manager/orchestration_stack.rb    | 5 +++--
 1 file changed, 3 insertions(+), 2 deletions(-)

https://github.com/ManageIQ/manageiq/pull/14421

For backward compatibility purpose the delete VMs at stack retirement feature is enabled by default only for product >= 5.8.

To manually turn on the feature for users on V5.7 the automate script needs a change as following:

Cloud/Orchestration/Retirement/Statemachines/Methods/remove_from_provider

change
stack.raw_delete_stack
to
stack.raw_delete_stack(true)

Note: above change can be applied for Azure stacks only. 

Need documentation update.

Vm as well as the service gets deleted when service is retired

I'm moving to verified per the expert.  Reopen if necessary as MS does change json from time to time.

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHSA-2017:0898