Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1934596 - On failed Azure VM creation we are leaving behind artifacts that need to be removed
Summary: On failed Azure VM creation we are leaving behind artifacts that need to be r...
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Compute Resources - Azure
Version: 6.8.0
Hardware: x86_64
OS: Linux
low
low
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Jitendra Yejare
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2021-03-03 14:42 UTC by Chris Roberts
Modified: 2022-10-28 18:04 UTC (History)
0 users

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-10-28 18:04:20 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)
screenshot of artifacts left behind (257.28 KB, image/png)
2021-03-03 14:42 UTC, Chris Roberts 		no flags Details
View All


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 32642 0 Normal New On failed Azure VM creation we are leaving behind artifacts that need to be removed 2021-05-20 17:52:56 UTC

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.
Note You need to log in before you can comment on or make changes to this bug.