Bug 1934596

Summary: On failed Azure VM creation we are leaving behind artifacts that need to be removed
Product: Red Hat Satellite Reporter: Chris Roberts <chrobert>
Component: Compute Resources - AzureAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED WONTFIX QA Contact: Jitendra Yejare <jyejare>
Severity: low Docs Contact:
Priority: low    
Version: 6.8.0Keywords: Triaged
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-10-28 18:04:20 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
screenshot of artifacts left behind none

Description Chris Roberts 2021-03-03 14:42:18 UTC
Created attachment 1760398 [details]
screenshot of artifacts left behind

Description of problem:
When a VM creation fails, we are leaving behind artifacts with the VM name in the Azure Resource Group. 

We clean up a few things such as the disk image and VM metadata object, but we are leaving behind the network interface and reserved public IP

Version-Release number of selected component (if applicable):

Satellite 6.8.x
Foreman-Azure-RM-2.1.2

How reproducible:


Steps to Reproduce:
1. Install Satellite and connect to Azure Compute Resource
2. Create a VM and cause it to fail for whatever reason
3. Check Azure portal and see artifacts left behind with the vmname

Actual results:
Reserved IP address and NIC are left behind in the Resource Group

Expected results:
On failed VM rollback we remove everything

Additional info:

Screenshot attached of failed VM artifacts left behind. 

If you need a way during testing for verification to cause a VM create to fail, reach out to me and I give a few examples.

Comment 1 Chris Roberts 2021-03-03 14:43:33 UTC
This is low severity since it does not cause any harm or cost left behind and is easy to clean them up.

Comment 2 Brad Buckingham 2022-09-02 20:25:18 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 3 Brad Buckingham 2022-09-02 20:30:13 UTC
Upon review of our valid but aging backlog the Satellite Team has concluded that this Bugzilla does not meet the criteria for a resolution in the near term, and are planning to close in a month. This message may be a repeat of a previous update and the bug is again being considered to be closed. If you have any concerns about this, please contact your Red Hat Account team.  Thank you.

Comment 4 Brad Buckingham 2022-10-28 18:04:20 UTC
Thank you for your interest in Red Hat Satellite. We have evaluated this request, and while we recognize that it is a valid request, we do not expect this to be implemented in the product in the foreseeable future. This is due to other priorities for the product, and not a reflection on the request itself. We are therefore closing this out as WONTFIX. If you have any concerns about this feel free to contact your Red Hat Account Team. Thank you.