Bug #2880
open
Openstack spawn failure can cause Foreman to lock thread(s) permanently
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.
Updated by Ohad Levy over 11 years ago
the timeout is 5 minutes, maybe you didnt wait that long?
Updated by Sam Kottler over 11 years ago
The tab was open for quite a while. This is a bug anyhow since the connect was initialized, the instance was created, failed to get created, and then foreman never noticed.
Updated by Ohad Levy over 11 years ago
can you try again, my past experience is that it get rolled back after 5 minutes...
Updated by Sam Kottler over 11 years ago
Yep, sure. My openstack instance is working nicely now, but I'll break it later today to reproduce this problem ;-)
Updated by
Updated by Stephen Benjamin over 10 years ago
I see this problem still. OpenStack was in a bad state (all instances immediately went to Error state), and Foreman never recovered.
Updated by Dominic Cleal about 10 years ago
- Category changed from Compute resources to Compute resources - OpenStack