yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

It's valid to have a compute service w/o a host mapping if the nova-
compute service was started but discover_hosts was not yet run, we
shouldn't block the compute service delete on that, so we should just
handle HostMappingNotFound and pass.

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

** Also affects: nova/queens
   Importance: Undecided
       Status: New

** Also affects: nova/pike
   Importance: Undecided
       Status: New

** Changed in: nova
     Assignee: Surya Seetharaman (tssurya) => Matt Riedemann (mriedem)

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

Title:
  Handle HostMappingNotFound when deleting a service

Status in OpenStack Compute (nova):
  Confirmed
Status in OpenStack Compute (nova) pike series:
  New
Status in OpenStack Compute (nova) queens series:
  New

Bug description:
  While deleting a service, we also try to delete the HostMapping before
  it here:
  https://github.com/openstack/nova/blob/fcf406003bcde2b60a515f694f2640e27a9d65fd/nova/api/openstack/compute/services.py#L243
  . However there could be a situation where we do not find the
  HostMapping (for instance when we run nova-manage cell_v2 delete_host
  before nova service-delete). This needs to be handled in the try catch
  block and if we do not find the host_mapping, we just need to proceed
  to deleting the service as opposed to the current behaviour where it
  gives a 500.

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