yahoo-eng-team team mailing list archive

[Tobias Urdin <2049903@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

if an operator has a compute node and reinstalls it but forget to do a
"openstack compute service delete <id>" first (that would wipe the nova-
compute service record and the resource provider in placement) the
reinstalled compute node with the same hostname happily reports it's
state as up even though the resource provider creation that nova-compute
tried failed due to a conflict with the resource providers.

to do operators a big favor we should make nova-compute startup fail if
the resource provider creation failed (like when there is a conflict)

** Affects: nova
     Importance: Undecided
         Status: In Progress

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

Title:
  nova-compute starts even if resource provider creation fails with
  conflict

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  if an operator has a compute node and reinstalls it but forget to do a
  "openstack compute service delete <id>" first (that would wipe the
  nova-compute service record and the resource provider in placement)
  the reinstalled compute node with the same hostname happily reports
  it's state as up even though the resource provider creation that nova-
  compute tried failed due to a conflict with the resource providers.

  to do operators a big favor we should make nova-compute startup fail
  if the resource provider creation failed (like when there is a
  conflict)

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