Project

General

Profile

Actions
Copy link

Bug #32642

open

On failed Azure VM creation we are leaving behind artifacts that need to be removed

Added by Chris Roberts almost 3 years ago. Updated almost 3 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
General Plugin Issues
Target version:
Backlog
Difficulty:
Triaged:
Yes
Bugzilla link:
1934596
Pull request:
Fixed in Releases:
Found in Releases:
2.2.4
Red Hat JIRA:

Description

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

Actions
Copy link
 #1

Updated by Chris Roberts almost 3 years ago

  • Found in Releases 2.2.4 added
Actions
Copy link

Also available in: Atom PDF