yahoo-eng-team team mailing list archive

[Bogdan Dobrelya <bdobrelia@xxxxxxxxxxxx>]

Hi, @Eric, no I didn't restart nova-conductor, should I? I will recheck
and update the bug, thank you. Perhaps, this bug has a doc impact, are
there any details in documentation?  If, not there should be an
updatedfor enable_new_services and nova-conductor.

** Also affects: openstack-manuals
   Importance: Undecided
       Status: New

** Changed in: openstack-manuals
       Status: New => Incomplete

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

Title:
  Nova doesn't honor enable_new_services=False

Status in OpenStack Compute (Nova):
  Incomplete
Status in OpenStack Manuals:
  Incomplete

Bug description:
  When specified enable_new_services=False for nova.conf at new node and
  started nova-compute service, the nova-compute service is shown
  'enabled' and 'up' in nova service-list output.

  But it is expected instead that the compute service will not register
  itself and will not be shown in nova-service list

  How to reproduce with existing compute node (Destructive! Use it only on test environments):
  1) stop nova-compute service
  2) remove nova-compute service from DB, for example node-foo:
  use nova;
  delete from compute_nodes where hypervisor_hostname='node-foo';
  delete from services where host='node-foo';
  3) Set enable_new_services=False in nova.conf
  4) start nova-compute service
  5) check nova service-list and launch instance, as an option

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