← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1780011] Re: OSA Queens: libvirtError: Failed to connect socket to '/var/run/libvirt/libvirt-sock': No such file or directory

 

Reviewed:  https://review.openstack.org/593001
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible-os_nova/commit/?id=da2b8f44440e92a9a25af17dd9737f7177d1e5bc
Submitter: Zuul
Branch:    master

commit da2b8f44440e92a9a25af17dd9737f7177d1e5bc
Author: Jesse Pretorius <jesse.pretorius@xxxxxxxxxxxxxxx>
Date:   Fri Aug 17 12:13:36 2018 +0100

    Ensure nova-compute service start after libvirtd
    
    This patch aims to ensure that the nova-compute systemd service is
    started only after the libvirtd systemd service.
    
    Closes-Bug: 1780011
    Co-Authored-By: kaiokassiano <kaiokmo@xxxxxxxxxxxxxxx>
    Change-Id: Ie9b6d83d4a9573be96e050376f756e97895b6e67


** Changed in: openstack-ansible
       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/1780011

Title:
  OSA Queens: libvirtError: Failed to connect socket to
  '/var/run/libvirt/libvirt-sock': No such file or directory

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

Bug description:
  I have installed stable/queens 17.0.5 using openstack-ansible on
  Ubuntu with ODL.

  When i reboot compute node, instances go in shut off state.

  Log in /var/log/nova/nova-compute.log:

  2018-07-04 10:00:58.496 5519 ERROR nova.virt.libvirt.host
  libvirtError: Failed to connect socket to '/var/run/libvirt/libvirt-
  sock': No such file or directory

  If power fluctuates compute will go down and i have to restart nova-
  compute on compute node and start all instances.

  Is there a fix for this issue?

  Status of services after reboot:

  root@home:~# service libvirtd status
  ● libvirtd.service - Virtualization daemon
     Loaded: loaded (/lib/systemd/system/libvirtd.service; enabled; vendor preset: enabled)
     Active: active (running) since Wed 2018-07-04 10:02:56 IST; 25s ago
       Docs: man:libvirtd(8)
             https://libvirt.org
   Main PID: 5809 (libvirtd)
      Tasks: 17 (limit: 32768)
     Memory: 25.0M
        CPU: 385ms
     CGroup: /system.slice/libvirtd.service
             └─5809 /usr/sbin/libvirtd

  Jul 04 10:02:54 home systemd[1]: Starting Virtualization daemon...
  Jul 04 10:02:56 home systemd[1]: Started Virtualization daemon.

  
  root@home:~# service nova-compute status
  ● nova-compute.service - nova openstack service
     Loaded: loaded (/etc/systemd/system/nova-compute.service; enabled; vendor preset: enabled)
     Active: inactive (dead) since Wed 2018-07-04 10:00:58 IST; 2min 30s ago
    Process: 5519 ExecStart=/openstack/venvs/nova-17.0.5/bin/nova-compute --log-file=/var/log/nova/nova-compute.log (code=exited, status=0/SUCCESS)
   Main PID: 5519 (code=exited, status=0/SUCCESS)

  Jul 04 10:00:53 home systemd[1]: Started nova openstack service.
  Jul 04 10:00:56 home nova-compute[5519]: /openstack/venvs/nova-17.0.5/lib/python2.7/site-packages/oslo_db/sqlalchemy/enginefacade.py:332: NotSupport
  Jul 04 10:00:56 home nova-compute[5519]:   exception.NotSupportedWarning

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


References