yahoo-eng-team team mailing list archive

[Matt Riedemann <mriedem.os@xxxxxxxxx>]

Public bug reported:

This came up in the mailing list:

http://lists.openstack.org/pipermail/openstack-
operators/2017-June/013765.html

And was agreed that it can be considered a bug that the
enable_new_services config option should only auto-disable new nova-
compute services:

http://lists.openstack.org/pipermail/openstack-
operators/2017-June/013771.html

It should not auto-disable things like nova-conductor, nova-scheduler or
nova-osapi_compute, since (1) it doesn't make sense to disable those and
(2) it just means the operator/admin has to enable them later to fix the
nova service-list output.

** Affects: nova
     Importance: Medium
     Assignee: Matt Riedemann (mriedem)
         Status: Triaged


** Tags: db

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

Title:
  enable_new_services=False should only auto-disable nova-compute
  services

Status in OpenStack Compute (nova):
  Triaged

Bug description:
  This came up in the mailing list:

  http://lists.openstack.org/pipermail/openstack-
  operators/2017-June/013765.html

  And was agreed that it can be considered a bug that the
  enable_new_services config option should only auto-disable new nova-
  compute services:

  http://lists.openstack.org/pipermail/openstack-
  operators/2017-June/013771.html

  It should not auto-disable things like nova-conductor, nova-scheduler
  or nova-osapi_compute, since (1) it doesn't make sense to disable
  those and (2) it just means the operator/admin has to enable them
  later to fix the nova service-list output.

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