yahoo-eng-team team mailing list archive

[OpenStack Infra <1712718@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.openstack.org/496995
Committed: https://git.openstack.org/cgit/openstack/nova/commit/?id=c19ebcbd58bc673e336bc5fa3b815c7b0a20d628
Submitter: Jenkins
Branch:    master

commit c19ebcbd58bc673e336bc5fa3b815c7b0a20d628
Author: He Jie Xu <hejie.xu@xxxxxxxxx>
Date:   Thu Aug 24 11:38:31 2017 +0800

    Remove allocation when booting instance rescheduled or aborted
    
    In Pike release, there is no auto-heal in the resource tracker.
    So when instance booting failed, the allocation records aren't
    cleaned up.
    
    This patch clean up the allocation records when the instance
    rescheduled and aborted.
    
    Change-Id: I95d2f4c9392883052188fb7901451530068502db
    Closes-Bug: #1712718


** Changed in: nova
       Status: In Progress => Fix Released

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1712718

Title:
  Allocations records aren't removed after rescheduling

Status in OpenStack Compute (nova):
  Fix Released
Status in OpenStack Compute (nova) pike series:
  In Progress

Bug description:
  When all the nodes are Pike release, the allocations records aren't
  removed from the destination host which failed to boot up the
  instance, after the instance are rescheduled in another host, the
  allocation records for the failed host still exists.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1712718/+subscriptions