yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: nova
       Status: Fix Committed => 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/1250049

Title:
  Recent change overwrites Admin set disabled status on libvirt error

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  A recent change https://review.openstack.org/#/c/52189/9  introduced
  the automatic disable / re-enable of nova-compute when connection to
  libvirt is lost and recovered.

  While the idea is a good one the implementation means that any
  existing disabled status is lost (its very common on a large system
  for specific  hosts to  have been disabled by an administrator for  a
  number of reasons, e.g. new servers still being commissioned, planned
  maintenance,  reserved capacity, etc).   As implemented this change
  will remove that disables status - returning nodes to the state where
  instances are scheduled to them even when the admin has explicit tried
  to prevent this.

  Suggest that this change is backed out and replaced by an additional
  status value on each service so that there is separation between
  manual service enable/disable and automatic enable/disable based on
  detected errors.

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