Ubuntu
libvirt package

systemctl enable libvirtd.service fails

Bug #1588004 reported by Chris J Arges
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
libvirt (Ubuntu)
Fix Released
High
Unassigned

Bug Description

$ sudo systemctl enable libvirtd.service
Synchronizing state of libvirtd.service with SysV service script with /lib/systemd/systemd-sysv-install.
Executing: /lib/systemd/systemd-sysv-install enable libvirtd
Failed to enable unit: Too many levels of symbolic links

This could potentially cause failures when upgrading from libvirt-1.3.4-1ubuntu3 to -1ubuntu4.

See original description
Revision history for this message
Chris J Arges (arges) wrote :

A manual fix for this:
  rm /etc/systemd/libvirtd.service /etc/systemd/system/multi-user.target.wants/libvirt-bin.service
  systemctl enable libvirtd.service

Revision history for this message
Chris J Arges (arges) wrote :

Possibly related:
https://github.com/systemd/systemd/issues/3010

However I cannot systemctl 'disable' then 'enable'.

Chris J Arges (arges)
description: updated
Revision history for this message
Stefan Bader (smb) wrote :

Problem here was that all the code that handles cleaning up old libvirt-bin references is done in the preinst script of libvirt-bin and only when upgrading from a version prior 1.3.3-2. The code to remove /etc/systemd/system/libvirtd.service -> /lib/systemd/system/libvirt-bin.service was only added in 1.3.4-1ubuntu3. So anybody having upgraded to 1.3.4 before would have that link and preinst would not clean up.
I have now added code that will check for various old files/links when upgrading from more recent versions (or even fresh install) and if they exist will remove them. That seems to recover from a partial migration.

Stefan Bader (smb)
Changed in libvirt (Ubuntu):
status: New → Triaged
importance: Undecided → High
Revision history for this message
Launchpad Janitor (janitor) wrote :

This bug was fixed in the package libvirt - 1.3.4-1ubuntu5

---------------
libvirt (1.3.4-1ubuntu5) yakkety; urgency=low

  * Update the correct apparmor profiles to allow AAVMF and qemu-efi
    firmware for aarch64 (1538882)
  * Clean up / refresh various patches to finalize switch from libvirt-bin
    to libvirtd as service name.
    Drop: d/p/ubuntu/libvirt-bin-service-libvirtd-alias.patch
    Refresh+Rename: d/p/ubuntu/libvirt-bin-service-set-notifyaccess.patch ->
                    d/p/ubuntu/libvirtd-service-nolimit.patch
    Rename: d/p/ubuntu/libvirt-bin-service-set-notifyaccess.patch ->
            d/p/ubuntu/libvirtd-service-set-notifyaccess.patch
    Refresh: d/p/ubuntu/libvirtd-service-add-bin-alias.patch
    Add: d/p/ubuntu/libvirtd-init-add-bin-alias.patch
  * Change default profile used by libvirtd.service to /etc/default/libvirtd.
    Drop: d/p/ubuntu/switch-service-files-to-libvirt-bin.patch
  * Drop virtlockd.service from dh_systemd_start in debian/rules as
    the service is socket activated (LP: #1588006).
  * Fix failure to enable libvirtd.service due to lingering libvirt-bin
    alias. This could happen when the upgrade from a version prior 1.3.3-2
    happened before 1.3.4-1ubuntu3 (LP: #1588004).

 -- Stefan Bader <email address hidden> Thu, 02 Jun 2016 14:50:27 +0200

Changed in libvirt (Ubuntu):
status: Triaged → Fix Released
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.