Project

General

Profile

Actions
Copy link

Bug #2880

open

Openstack spawn failure can cause Foreman to lock thread(s) permanently

Added by Sam Kottler almost 12 years ago. Updated over 10 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Compute resources - OpenStack
Target version:
-
Difficulty:
Triaged:
Bugzilla link:
Pull request:
Fixed in Releases:
Found in Releases:
Red Hat JIRA:

Description

If spawning on an openstack compute resource fails, Foreman will consume the thread it was utilizing at the time of failure and never release it. The expected behavior is that the orchestration stack would roll back the creation process and things would carry on as usual.

Actions
Copy link

Also available in: Atom PDF