[Bug 1618812] Re: nova-scheduler autopkgtest fails

[Launchpad Bug Tracker]

This bug was fixed in the package nova - 2:14.0.0-0ubuntu1

---------------
nova (2:14.0.0-0ubuntu1) yakkety; urgency=medium

  * New upstream release for OpenStack Newton.
  * d/t/nova-compute-daemons: Skip test execution if running within a
    container, ensuring that autopkgtests don't fail on armhf and s390x.
  * d/t/control,nova-compute-daemons: Don't install nova-compute as part
    of the autopkgtest control setup, direct install hypervisor specific
    nova-compute packages ensuring packages are configured in the correct
    order and that nova-compute can access the libvirt socket.

 -- James Page <james.page at ubuntu.com>  Fri, 07 Oct 2016 08:48:28 +0100

** Changed in: nova (Ubuntu)
       Status: Triaged => Fix Released

-- 
You received this bug notification because you are a member of Ubuntu
OpenStack, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1618812

Title:
  nova-scheduler autopkgtest fails

Status in nova package in Ubuntu:
  Fix Released

Bug description:
  nova has auto package test checking that daemons are started out of
  the box.

  debian/tests/nova-daemons checks a bunch of them.

  However nova-scheduler fails to start with CantStartEngineError No
  sql_connection parameter is established.

  Either sql needs to be setup for nova-schedular test, or nova-
  scheduler should be dropped from the basic nova-daemons test.

  See attached journal entries.

  Investigating further, restarting nova-scheduler after dpkg run is
  complete succeeds fine. And this autopkgtest failure is only seen on
  very fast s390x with huge I/O co-processors and caches.

  Adding sync call after nova-manage db sync appears to resolve the
  issue.

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