yahoo-eng-team team mailing list archive

[Balazs Gibizer <1886418@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

Steps to reproduce
==================
* Create a single host devstack
In quick succession (in less time than [compute]/update_resources_interval config)
* Make sure that you can boot a server on the single compute
* Set the compute service status to disabled
* Make sure that the COMPUTE_STATUS_DISABLED in added to the compute RP in placement and therefore you cannot create servers any more
* Set the compute service status to enabled
* create a new server

Expected result
===============
the server is created successfully 

Actual result
=============
The server creation fails with NoValidHost because the COMPUTE_STATUS_DISABLED wasn't removed from the compute RP due to generation conflict.

** Affects: nova
     Importance: Low
     Assignee: Balazs Gibizer (balazs-gibizer)
         Status: New

** Changed in: nova
     Assignee: (unassigned) => Balazs Gibizer (balazs-gibizer)

** Changed in: nova
   Importance: Undecided => Low

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

Title:
  Enabled compute service still have COMPUTE_STATUS_DISABLED trait and
  therefore ignored by the scheduler

Status in OpenStack Compute (nova):
  New

Bug description:
  Steps to reproduce
  ==================
  * Create a single host devstack
  In quick succession (in less time than [compute]/update_resources_interval config)
  * Make sure that you can boot a server on the single compute
  * Set the compute service status to disabled
  * Make sure that the COMPUTE_STATUS_DISABLED in added to the compute RP in placement and therefore you cannot create servers any more
  * Set the compute service status to enabled
  * create a new server

  Expected result
  ===============
  the server is created successfully 

  Actual result
  =============
  The server creation fails with NoValidHost because the COMPUTE_STATUS_DISABLED wasn't removed from the compute RP due to generation conflict.

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