yahoo-eng-team team mailing list archive

[Michael <1898553@xxxxxxxxxxxxxxxxxx>]

Public bug reported:

hello,

after upgrading from Openstack Train to Ussuri, running on Ubuntu 18.04,
the nova-compute service doesn't start due to the libvirtd service not
starting because of the --listen option being enabled in the
/etc/default/libvirtd file and so, the nova-compute service fail to
reach the socket that doesn't exist.

i have found other bug report and patch that claim to have fixed this
issue but it's not, at least not on the package installed version of
openstack on ubuntu 18.04 (https://bugs.launchpad.net/puppet-
nova/+bug/1880619)

is nova-compute able to use another mechanism to connect to libvirtd ?
and thus not needing the --listen option ?

** Affects: nova
     Importance: Undecided
         Status: New

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

Title:
  nova-compute doesn't start due to libvirtd --listen restriction

Status in OpenStack Compute (nova):
  New

Bug description:
  hello,

  after upgrading from Openstack Train to Ussuri, running on Ubuntu
  18.04, the nova-compute service doesn't start due to the libvirtd
  service not starting because of the --listen option being enabled in
  the /etc/default/libvirtd file and so, the nova-compute service fail
  to reach the socket that doesn't exist.

  i have found other bug report and patch that claim to have fixed this
  issue but it's not, at least not on the package installed version of
  openstack on ubuntu 18.04 (https://bugs.launchpad.net/puppet-
  nova/+bug/1880619)

  is nova-compute able to use another mechanism to connect to libvirtd ?
  and thus not needing the --listen option ?

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