Unknown packages required for sys-net based on fedora-25-minimal

[andrewdavidwong]

Qubes OS version (e.g., R3.2):

R3.2

Affected TemplateVMs (e.g., fedora-23, if applicable):

fedora-25
fedora-25-minimal

---

Expected behavior:

sys-net works when based on fedora-25.

Actual behavior:

AppVMs have no network connectivity when sys-net is based on fedora-25.

Steps to reproduce the behavior:

Base sys-net on fedora-25.

General notes:

Since Fedora 24 reached EOL on 2017-08-08, Fedora 25 is now the only available Fedora template for R3.2.

---

Related issues:

#2964 (4.0-rc1, concerns both fedora-25 and debian-9)

[marmarek]

I've tried to reproduce this and failed.
I've got fresh qubes-template-fedora-25 from repository, installed updates there (dnf update), then switched sys-net to fedora-25. And everything works just fine...

[marmarek]

I've tried to reproduce this and failed.
I've got fresh qubes-template-fedora-25 from repository, installed updates there (dnf update), then switched sys-net to fedora-25. And everything works just fine...

[0spinboson]

Marek: I had no issues using my upgraded f-24-m template when I switched to it shortly before switching to R4.0rc1, but the fresh 4.0 fc25 template doesn't work as sys-net on two different machines, and I recall having trouble with the fc25m template under R3.2 as well, when I tried it once before, months ago. (Didn't investigate it further or mention it because I didn't have time and I thought it was just me having broken something or missing the obvious or whatever.)

[0spinboson]

Marek: I had no issues using my upgraded f-24-m template when I switched to it shortly before switching to R4.0rc1, but the fresh 4.0 fc25 template doesn't work as sys-net on two different machines, and I recall having trouble with the fc25m template under R3.2 as well, when I tried it once before, months ago. (Didn't investigate it further or mention it because I didn't have time and I thought it was just me having broken something or missing the obvious or whatever.)

[andrewdavidwong]

@marmarek: You're right. I can no longer reproduce this with vanilla fedora-25. The problem only occurs when I try to use the NetVM-specific template I upgraded from Fedora 24 (originally based on fedora-24-minimal). This suggests that some packages are missing, which means we should update the Fedora-minimal documentation once we find out what they are.

[andrewdavidwong]

@marmarek: You're right. I can no longer reproduce this with vanilla fedora-25. The problem only occurs when I try to use the NetVM-specific template I upgraded from Fedora 24 (originally based on fedora-24-minimal). This suggests that some packages are missing, which means we should update the Fedora-minimal documentation once we find out what they are.

[marmarek]

If that is just about missing package, comparing list of packages should give some hints.

[marmarek]

If that is just about missing package, comparing list of packages should give some hints.

[0spinboson]

I was playing around with debian-8 template a bit, and I noticed that after updating a bunch of packages using jessie-backports, one of which being salt-common-2016.11.2 (from salt-common-2014.1.13), the next time I started sys-net, networking was broken. Networking is also broken using d9 for me. Could this be related?

(I had a look at the package lists for f25 and f25m, but none of the differences seem to me to be likely to be the cause, which suggests it's a dependency causing the issue. F25 uses 2016.11.3, d9 11.2. Having said that, I see that fc24 also uses 2016.11, so I guess this is unlikely to be related.)

FWIW / in the interest of completeness, once I upgrade these, I can no longer use d8 as netvm:

sudo apt upgrade -t jessie-backports salt-common salt-ssh
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... The following packages were automatically installed and are no longer required:
libasprintf0c2 libegl1-mesa-drivers libelfg0 libllvm3.5 libopenvg1-mesa libuuid-perl libwayland-egl1-mesa python-defusedxml python-soappy python-wstools sshpass
Use 'apt-get autoremove' to remove them.
Done
The following NEW packages will be installed:
emacs24-el firmware-amd-graphics firmware-misc-nonfree javascript-common libapparmor1 libdrm-amdgpu1 libfastjson4 libgphoto2-port12 libjs-jquery libjs-sphinxdoc libjs-underscore libldap-common libllvm3.8 liblognorm5 libseccomp2 libsensors4 libsoxr0 libxss1 linux-compiler-gcc-4.9-x86 linux-headers-4.9.0-0.bpo.3-amd64 linux-headers-4.9.0-0.bpo.3-common linux-image-4.9.0-0.bpo.3-amd64 linux-kbuild-4.9 python-backports-abc python-cffi-backend python-concurrent.futures python-croniter python-cryptography python-dateutil python-enum34 python-httplib2 python-idna python-ipaddress python-ndg-httpsclient python-openssl python-pyasn1 python-pysimplesoap python-requests python-setuptools python-singledispatch python-tornado python-tz python-urllib3

The following packages have been kept back:
debugedit librpm3 librpmbuild3 librpmio3 python-rpm rpm rpm-common rpm2cpio

The following packages will be upgraded:
bash-completion cups cups-client cups-common cups-core-drivers cups-daemon cups-ppdc cups-server-common dh-python dkms dmidecode e2fslibs e2fsprogs emacs24 emacs24-bin-common emacs24-common exfat-fuse exfat-utils exim4 exim4-base exim4-config exim4-daemon-light firmware-linux firmware-linux-nonfree geoip-database gettext-base i965-va-driver ifupdown irqbalance iucode-tool keepassx libasprintf0c2 libassuan0 libbluray1 libcomerr2 libcups2 libcupscgi1 libcupsimage2 libcupsmime1 libcupsppdc1 libdrm-intel1 libdrm-nouveau2 libdrm-radeon1 libdrm2 libegl1-mesa libegl1-mesa-drivers libfftw3-double3 libfftw3-single3 libgbm1 libgcrypt20 libgeoip1 libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa libglib2.0-0 libglib2.0-bin libglib2.0-data libgpg-error0 libgphoto2-6 libgphoto2-l10n libgusb2 libksba8 libldap-2.4-2 libllvm3.5 libnet-dbus-perl libpam-systemd libpcap0.8 libpulse-mainloop-glib0 libpulse0 libpulsedsp libsqlite3-0 libss2 libssl1.0.0 libsystemd0 libudev1 libva1 libvdpau1 libwayland-egl1-mesa libxatracker2 linux-base linux-headers-amd64 linux-image-amd64 linux-libc-dev manpages manpages-dev openssl pinentry-gtk2 pulseaudio pulseaudio-module-x11 pulseaudio-utils python-daemon python-debianbts python-jinja2 python-lockfile python-msgpack python-pil python-pkg-resources python-pygments python-reportbug python-six python3-pkg-resources python3-six reportbug rsyslog salt-common salt-ssh shared-mime-info socat systemd systemd-sysv tar udev usb-modeswitch usb-modeswitch-data va-driver-all vdpau-va-driver xserver-xorg-video-ati xserver-xorg-video-intel xserver-xorg-video-radeon
119 upgraded, 43 newly installed, 0 to remove and 8 not upgraded.

[0spinboson]

I was playing around with debian-8 template a bit, and I noticed that after updating a bunch of packages using jessie-backports, one of which being salt-common-2016.11.2 (from salt-common-2014.1.13), the next time I started sys-net, networking was broken. Networking is also broken using d9 for me. Could this be related?

(I had a look at the package lists for f25 and f25m, but none of the differences seem to me to be likely to be the cause, which suggests it's a dependency causing the issue. F25 uses 2016.11.3, d9 11.2. Having said that, I see that fc24 also uses 2016.11, so I guess this is unlikely to be related.)

FWIW / in the interest of completeness, once I upgrade these, I can no longer use d8 as netvm:

sudo apt upgrade -t jessie-backports salt-common salt-ssh
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... The following packages were automatically installed and are no longer required:
libasprintf0c2 libegl1-mesa-drivers libelfg0 libllvm3.5 libopenvg1-mesa libuuid-perl libwayland-egl1-mesa python-defusedxml python-soappy python-wstools sshpass
Use 'apt-get autoremove' to remove them.
Done
The following NEW packages will be installed:
emacs24-el firmware-amd-graphics firmware-misc-nonfree javascript-common libapparmor1 libdrm-amdgpu1 libfastjson4 libgphoto2-port12 libjs-jquery libjs-sphinxdoc libjs-underscore libldap-common libllvm3.8 liblognorm5 libseccomp2 libsensors4 libsoxr0 libxss1 linux-compiler-gcc-4.9-x86 linux-headers-4.9.0-0.bpo.3-amd64 linux-headers-4.9.0-0.bpo.3-common linux-image-4.9.0-0.bpo.3-amd64 linux-kbuild-4.9 python-backports-abc python-cffi-backend python-concurrent.futures python-croniter python-cryptography python-dateutil python-enum34 python-httplib2 python-idna python-ipaddress python-ndg-httpsclient python-openssl python-pyasn1 python-pysimplesoap python-requests python-setuptools python-singledispatch python-tornado python-tz python-urllib3

The following packages have been kept back:
debugedit librpm3 librpmbuild3 librpmio3 python-rpm rpm rpm-common rpm2cpio

The following packages will be upgraded:
bash-completion cups cups-client cups-common cups-core-drivers cups-daemon cups-ppdc cups-server-common dh-python dkms dmidecode e2fslibs e2fsprogs emacs24 emacs24-bin-common emacs24-common exfat-fuse exfat-utils exim4 exim4-base exim4-config exim4-daemon-light firmware-linux firmware-linux-nonfree geoip-database gettext-base i965-va-driver ifupdown irqbalance iucode-tool keepassx libasprintf0c2 libassuan0 libbluray1 libcomerr2 libcups2 libcupscgi1 libcupsimage2 libcupsmime1 libcupsppdc1 libdrm-intel1 libdrm-nouveau2 libdrm-radeon1 libdrm2 libegl1-mesa libegl1-mesa-drivers libfftw3-double3 libfftw3-single3 libgbm1 libgcrypt20 libgeoip1 libgl1-mesa-dri libgl1-mesa-glx libglapi-mesa libglib2.0-0 libglib2.0-bin libglib2.0-data libgpg-error0 libgphoto2-6 libgphoto2-l10n libgusb2 libksba8 libldap-2.4-2 libllvm3.5 libnet-dbus-perl libpam-systemd libpcap0.8 libpulse-mainloop-glib0 libpulse0 libpulsedsp libsqlite3-0 libss2 libssl1.0.0 libsystemd0 libudev1 libva1 libvdpau1 libwayland-egl1-mesa libxatracker2 linux-base linux-headers-amd64 linux-image-amd64 linux-libc-dev manpages manpages-dev openssl pinentry-gtk2 pulseaudio pulseaudio-module-x11 pulseaudio-utils python-daemon python-debianbts python-jinja2 python-lockfile python-msgpack python-pil python-pkg-resources python-pygments python-reportbug python-six python3-pkg-resources python3-six reportbug rsyslog salt-common salt-ssh shared-mime-info socat systemd systemd-sysv tar udev usb-modeswitch usb-modeswitch-data va-driver-all vdpau-va-driver xserver-xorg-video-ati xserver-xorg-video-intel xserver-xorg-video-radeon
119 upgraded, 43 newly installed, 0 to remove and 8 not upgraded.

[andrewdavidwong]

@marmarek: The original problem recurred again for me. Now that my sys-net is based on fedora-25, it frequently fails to connect to any network after the system resumes from sleep (reported separately in #3030). When this happens, I have to restart sys-net. After restarting it once today, I found find that (as originally described here) AppVMs had no network connectivity even though sys-net itself could ping sites and the qubes-firewall service was running fine in sys-firewall.

[andrewdavidwong]

@marmarek: The original problem recurred again for me. Now that my sys-net is based on fedora-25, it frequently fails to connect to any network after the system resumes from sleep (reported separately in #3030). When this happens, I have to restart sys-net. After restarting it once today, I found find that (as originally described here) AppVMs had no network connectivity even though sys-net itself could ping sites and the qubes-firewall service was running fine in sys-firewall.

[jpbrown-15]

This looks similar to the problem listed in the user forum. I didn't look at the Salt package but I have experienced a failure of all templates other than the originals provided with the 3.2 release to act as a NetVM. I have been able to do updates to the templates but if they weren't part of the original release, I have never been able to successfully get the network to function.

https://groups.google.com/forum/#!topic/qubes-users/hSTvQEiPxfU

[jpbrown-15]

This looks similar to the problem listed in the user forum. I didn't look at the Salt package but I have experienced a failure of all templates other than the originals provided with the 3.2 release to act as a NetVM. I have been able to do updates to the templates but if they weren't part of the original release, I have never been able to successfully get the network to function.

https://groups.google.com/forum/#!topic/qubes-users/hSTvQEiPxfU

[andrewdavidwong]

@jpbrown-15 It's possible that you're experiencing #3008 (of which #3030 turned out to be a duplicate).

[andrewdavidwong]

@jpbrown-15 It's possible that you're experiencing #3008 (of which #3030 turned out to be a duplicate).