nova-daemons autopkgtest is flaky

[Martin Pitt]

The "nova-daemons" autopkgtest often fails like this:

autopkgtest [00:44:02]: test nova-daemons: [-----------------------
OK
OK
OK
OK
ERROR: nova-console IS NOT RUNNING

This is particularly obvious on http://autopkgtest.ubuntu.com/packages/n/nova/yakkety/s390x/ which is a really fast architecture. But it occasionally happens on the other arches as well (check the autopkgtest history).

[James Page (james-page)]

I've pushed a commit to the git repo to install rabbitmq-server, which I think is the cause of the daemons shutting down esp on faster systems; this should resolve the race, as each daemon will be able to startup and connect to RMQ ok.

[Launchpad Janitor (janitor)]

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 <email address hidden> Fri, 07 Oct 2016 08:48:28 +0100