yahoo-eng-team team mailing list archive

[Alex Xu <soulxu@xxxxxxxxx>]

Public bug reported:

Currently the update_available_resource only update the instance which
still located on the host.

This leads after resize, still have allocation record on the old host.
Also when instance removed locally from db and compute node is offline,
after comptue node startup, the allocation record won't be cleanup.

** Affects: nova
     Importance: Undecided
     Assignee: Alex Xu (xuhj)
         Status: Invalid

** Changed in: nova
     Assignee: (unassigned) => Alex Xu (xuhj)

** Changed in: nova
       Status: New => Invalid

-- 
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/1622831

Title:
  The allocation record can't be removed after migration/failure

Status in OpenStack Compute (nova):
  Invalid

Bug description:
  Currently the update_available_resource only update the instance which
  still located on the host.

  This leads after resize, still have allocation record on the old host.
  Also when instance removed locally from db and compute node is
  offline, after comptue node startup, the allocation record won't be
  cleanup.

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