On Mon, Aug 28, 2017 at 7:46 AM, Tom Horsley <horsley1953@gmail.com> wrote:

On Mon, 28 Aug 2017 07:11:59 -0500
Richard Shaw wrote:

> Was RPM being updated in the same transaction? This bug[1] seems to
> indicate that the database being updated can cause this problem...

Yep, looks like rpm shows up in the log as being updated, though
I have never actually figured out what the heck akmod does and if
it is part of the same transaction or not. If I poke around on
the system during the dnf update, I see akmod build the new
nvidia driver while dnf update is still running, so I'm not
sure how an rpm that didn't exist at the start of the dnf update
could be part of the same transaction :-).

It's not part of the same transaction unfortunately. To do that would require a dnf plugin that no one has written yet.

akmods basically runs dnf in nohup so it will sit there and wait until the current transaction completes, which is why you have to be careful to wait for a while before you reboot.

Thanks,

Richard