Uploaded image for project: 'RHEL'
  1. RHEL
  2. RHEL-22597

VM can't autostart after Leapp upgrade

    • leapp-repository-0.20.0
    • Yes
    • Critical
    • Regression
    • rhel-sst-upgrades
    • 26
    • None
    • False
    • Hide

      None

      Show
      None
    • None
    • None
    • Rejected Blocker
    • Pass
    • None
    • All
    • None

      What were you trying to do that didn't work?

      Use an autostarted VM after the Leapp upgrade.

      Please provide the package NVR for which bug is seen:

      libvirt-8.0.0-23.module+el8.10.0+21023+5962ee04
      leapp-upgrade-el8toel9-0.19.0-9.el8

      How reproducible:

      100%

      Steps to reproduce

      1. On a recent 8.10 installation, create a VM with an pci hostdev and attached to the default NAT network
      2. Mark the VM as autostart, reboot host and confirm it's autostarted
      3. Run the leapp upgrade

      Expected results

      After the final reboot, when I log in the VM is running

      Actual results

      The VM is not running. The log complains about connection issues with virtnetworkd-sock which is weird because 8.10 has the monolithic libvirtd daemon and should run also libvirtd monolithically on the target 9.4.

      After starting the virtnetworkd manually the VM can start.

      Additional info:

      1. it was found when upgrading 8.10->9.4; it reproduces when upgrading 8.10 -> 9.3 with libvirt-9.5.0-7.el9_3.s390x
      2. it doesn't reproduce when upgrading 8.9 -> 9.3
        • libvirt-8.0.0-22.module+el8.9.0+19544+b3045133, leapp-upgrade-el8toel9-0.19.0-1.el8
      3. # systemctl status virtnetworkd
        ○ virtnetworkd.service - libvirt network daemon
             Loaded: loaded (/usr/lib/systemd/system/virtnetworkd.service; disabled; preset: disabled)
             Active: inactive (dead)
        TriggeredBy: ○ virtnetworkd-ro.socket
                     ○ virtnetworkd-admin.socket
                     ○ virtnetworkd.socket
               Docs: man:virtnetworkd(8)
                     https://libvirt.org/
        
        journalctl -u virtqemud:
        
        2032]: Failed to connect socket to '/var/run/libvirt/virtnetworkd-sock': No such file or directory
        2032]: Failed to connect socket to '/var/run/libvirt/virtnetworkd-sock': No such file or directory
        2032]: Failed to connect socket to '/var/run/libvirt/virtnetworkd-sock': No such file or directory
        2032]: Unable to release network device '<null>'
        2032]: internal error: Failed to autostart VM 'rhel9': Failed to connect socket to '/var/run/libvirt/virtnetworkd-sock': No s>
        2032]: Failed to connect socket to '/var/run/libvirt/virtnetworkd-sock': No such file or directory
        2032]: Failed to connect socket to '/var/run/libvirt/virtnetworkd-sock': No such file or directory
        2032]: Failed to connect socket to '/var/run/libvirt/virtnetworkd-sock': No such file or directory
        2032]: Unable to release network device '<null>'

              rh-ee-mmatuska Matej Matuska
              smitterl@redhat.com Sebastian Mitterle
              leapp-notifications leapp-notifications
              Lili Zhu Lili Zhu
              Miriam Portman Miriam Portman
              Votes:
              0 Vote for this issue
              Watchers:
              11 Start watching this issue

                Created:
                Updated:
                Resolved: