VMs left in error state if node failed to create

Bug #1847676 reported by Duc Truong
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
senlin
Fix Released
Undecided
Unassigned

Bug Description

When a scale out command tries to create a new node and it fails due to capacity (no valid host found), the VM is left in error after the scale out command fails.

VMs should not be left in error state in nova. Instead senlin should delete those VMs that failed to be created and are in error state.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to senlin (master)

Reviewed: https://review.opendev.org/688006
Committed: https://git.openstack.org/cgit/openstack/senlin/commit/?id=60fd3ff874600c4f3b23b657dcb617f4fecf891b
Submitter: Zuul
Branch: master

commit 60fd3ff874600c4f3b23b657dcb617f4fecf891b
Author: Duc Truong <email address hidden>
Date: Thu Oct 10 22:02:51 2019 +0000

    Delete VMs in error state after creation

    If a server create ends up with the server in error state, delete the
    server.

    Change-Id: I43afa5f393cd8475d2686f1e61d96ec79dac00cd
    Closes-Bug: #1847676

Changed in senlin:
status: New → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.