On Mon, 2020-01-13 at 12:18 +0100, Erik Skultety wrote:
On Fri, Jan 10, 2020 at 05:03:35PM +0100, Andrea Bolognani wrote:
From time to time we hit
FIY this has been fixed in both Fedora 30 and 31, so the workaround is no longer necessary
Either me or Dan hit it very recently IIRC. I don't feel like investing time into trying that again to prove that it was indeed the case, sorry O:-) Possibly what happened is that, even though the issue has been fixed in a recent dnf version, when you perform a network-based install you get the old dnf (which still has the issue) so at least the first update round needs the workaround.
IIUC it could have been any core package not just kernel, are we going to adopt a similar workaround for systemd packages as well?
I don't think anyone ever hit the issue with non-kernel packages, so I see no reason to proactively expand the scope of the workaround. -- Andrea Bolognani / Red Hat / Virtualization