yahoo-eng-team team mailing list archive

[OpenStack Infra <1898553@xxxxxxxxxxxxxxxxxx>]

Reviewed:  https://review.opendev.org/749603
Committed: https://git.openstack.org/cgit/openstack/puppet-nova/commit/?id=a44641df76730484ec82d119c9473251bee7ad72
Submitter: Zuul
Branch:    master

commit a44641df76730484ec82d119c9473251bee7ad72
Author: Tobias Urdin <tobias.urdin@xxxxxxxxx>
Date:   Thu Sep 3 01:19:05 2020 +0200

    Ubuntu has libvirt 6.0
    
    The UCA repo has libvirt 6.0 from Ussuri
    on Bionic and later.
    
    Closes-Bug: #1898553
    Change-Id: I8146f5b073e812f3cac472fc5e27976f17d248b4


** Changed in: puppet-nova
       Status: In Progress => 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/1898553

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

Status in OpenStack Compute (nova):
  Invalid
Status in puppet-nova:
  Fix Released

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