Error output during F31 -> F32 transition on T490

[conorsch]

Discovered during testing of #647. During the fedora-31 -> fedora-32 transition, sys-net became stuck in a reboot loop, complaining about an unknown PCI device.

The screen eventually filled up completely with those toast notifications. Trying to stop sys-net via qvm-kill had no effect. Tried also killing sys-usb & sys-firewall, but sys-net was repeatedly autostarted, because the updater was optimistically trying to proceed.

After a reboot of the entire machine, the sys VMs were properly configured with F32 and showed no problems whatsoever. Subsequent GUI updater runs completed without error. Network connectivity in other VMs worked without issue.

During extensive testing of #642 on a T480, I never encountered this problem. @emkll also has a T490 available for testing, and may be able to confirm this behavior. If so, let's get some more devices in the team's hands. One thought that occurs if it's T490 specific is the workaround to sys-net described in freedomofpress/securedrop-workstation-docs#62

[emkll]

I've observed those same errors locally. For me, the F31-F32 happened smoothly, and the error was observed in a subsequent update run, as the AppVMs were rebooted (2-3 days later, with some changes in dom0 in between). A full reboot of the workstation resolved, and subsequent updater runs (including VM reboots) now occur without error.

[conorsch]

Just now, I performed a fresh install of 0.5.1 (in preparation for testing 0.5.2), and on the clean install run, F31-based sys VMs were migrated to F32 without issue. So, failed reproduction on my end, too. Will report back if future update runs show it again.

[conorsch]

We're on F33 now and looking to move to F34 (#735), so closing as moot.