yahoo-eng-team team mailing list archive

[Thierry Carrez <thierry.carrez+lp@xxxxxxxxx>]

** Changed in: nova
       Status: Fix Committed => Fix Released

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

Title:
  grizzly uses FQDN for services

Status in OpenStack Compute (Nova):
  Fix Released

Bug description:
  grizzly has started using FQDN for nova services as opposed to short
  hostname. This means that anyone upgrading from Folsom will end up
  with a double list of services. e.g.:

  root@api01:~# nova-manage service list
  Binary           Host                                 Zone             Status     State Updated_At
  nova-consoleauth api01                                internal         enabled    XXX   2013-03-07 02:04:42
  nova-scheduler   api01                                internal         enabled    XXX   2013-03-07 02:04:42
  nova-scheduler   api01.sy3.aptira.com                 internal         enabled    :-)   2013-03-07 02:09:29
  nova-consoleauth api01.sy3.aptira.com                 internal         enabled    :-)   2013-03-07 02:09:29

  If the user is running a large installation this will result in a
  massive list of double services.

  Please consider updating nova-manage db sync such that it either
  removes all existing services in the nova.services table or that it
  updates the entries in the table to match the FQDN.

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