Bug 1348718

Dan, this might be something that Bill Fitz should look at if it's specific to retirement.  Take a look and see if it should be reassigned his way.

Greg, I suspect this is an issue for Bill Fitz, since Azure doesn't automatically delete associated resources.

hi Dan
Please let me know when the nested delete functionality has been added to the Azure-armrest gem.

Thank you
Bronagh

Added Polarion test case

*** Bug 1342640 has been marked as a duplicate of this bug. ***

(In reply to Bronagh Sorota from comment #5)
> hi Dan
> Please let me know when the nested delete functionality has been added to
> the Azure-armrest gem.
> 
> Thank you
> Bronagh

This functionality is now available in azure-armrest 0.3.12. Please see the VirtualMachineService#delete_associated_resources method.

New commit detected on ManageIQ/manageiq-providers-azure/master:
https://github.com/ManageIQ/manageiq-providers-azure/commit/3c3336a621356d60fe289e00ebde300560cffa39

commit 3c3336a621356d60fe289e00ebde300560cffa39
Author:     Bronagh Sorota <bsorota>
AuthorDate: Tue Nov 29 11:53:51 2016 -0500
Commit:     Bronagh Sorota <bsorota>
CommitDate: Tue Nov 29 11:54:02 2016 -0500

    Delete associated resources (NIC, IP, VHD, .status)
    when deleting a VM
    
    https://bugzilla.redhat.com/show_bug.cgi?id=1348718

 app/models/manageiq/providers/azure/cloud_manager/vm/operations.rb | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

I don't know this matters or not, but the disk doesn't get deleted using Retire or Delete from the power menu.  And the disk can show up in any of the storage accounts depending on how the VM was created so you will probably need to explicitly extract the disk location.

I'm afraid it's still not working in 58004.  Here are the gem versions

gem list
azure-armrest (0.5.2)
azure-signature (0.2.3)

Delete deletes the VM, but not the collateral resources.

Jeff
I just deleted a VM from CF and the VHD was removed from the storage account in Azure.
Can you list the steps you took to test this BZ? Did you check for the removal of the VHD in: the storage_account_name/blobs/manageiq on the Azure portal?

Are you hardcoded to storage_account_name/blobs/manageiq, specifically, the manageiq part?  The vhd can be located anywhere, and for us, I'm certain we don't store it there for these tests.

So, I'm only seeing these two commands in the log, both of which are working.  There does not appear to be a third one deleting the VHD.  Find me when you get in and we can try again.  I have 5.8.0.11 on 10.16.6.115

[root@10-16-6-115 log]# cat azure.log | grep RestClient.delete
RestClient.delete "https://management.azure.com/subscriptions/xxxxxxxx-b20e-48bd-a0c8-879c6dbcbfbb/resourceGroups/automation/providers/Microsoft.Compute/virtualMachines/avhddel1?api-version=2017-03-30", "Accept"=>"application/js............
RestClient.delete "https://management.azure.com/subscriptions/xxxxxxxx-b20e-48bd-a0c8-879c6dbcbfbb/resourceGroups/Automation/providers/Microsoft.Network/networkInterfaces/avhddel1-nic?api-version=2017-04-01", "Accept"=>"application/js.......

Adding the need info.  There must be some reason why it is intermittant.

Hi Jeff,
During VM provisioning we always place the newly provisioned VM's VHD in the above referenced location. 
Which tool are you using to create the VM used in these tests?

Thanks
Bronagh

Note that this feature is for CFME VMs created using Lifecycle provisioning.  The Azure orchestration script may use a different storage location.  Tested with 5.8.0.11 and all VM related items are now removed on a VM delete.

Moving to verified.