Hi, On Wed, Apr 17, 2019 at 02:47:41PM -0400, Sam Hartman wrote: > but I haven't been able to reproduce on a clean install. > It's frustrating: on my machines where I really want the upgrade to be > smoothe this bit me, but on all my toy tests, it didn't happen. > What I think may be necessary is for virtlogd to be active. > So it may be necessary to actually get libvirtd running and actually > running a VM to use the socket before the issue comes up.
That's possible. > Alternatively, it's possible some other change has fixed this in the > last month. We did not change anything in that area so it's likely hidden (e.g. only happening when running a VM) - I'll check that. > I'll certainly say that a month ago ran into this on two different VM > servers. That's an important data point. Thanks -- Guido
