Comment 6 for bug 1927745

Testing was kind of successful, in the sense that the patch fixes the problem. But I found a pre-existing bug in the packaging that manifested itself in this testing.

After upgrading the packages, not all services are restarted. Critically for this bug we are addressing here, rpc.gssd is not restarted:

Before upgrade:
  442 ? Ss 0:00 /usr/sbin/blkmapd
 7146 ? Ss 0:00 /usr/sbin/rpc.gssd
 7399 ? Ss 0:00 /usr/sbin/rpc.idmapd
 7406 ? Ss 0:00 /usr/sbin/rpc.mountd --manage-gids
 7400 ? Ss 0:00 /usr/sbin/rpc.svcgssd

After pkg upgrade:
  442 ? Ss 0:00 /usr/sbin/blkmapd
 7146 ? Ss 0:00 /usr/sbin/rpc.gssd
 8421 ? Ss 0:00 /usr/sbin/rpc.idmapd
 8422 ? Ss 0:00 /usr/sbin/rpc.mountd --manage-gids
 8420 ? Ss 0:00 /usr/sbin/rpc.svcgssd

We can see that blkmapd and rpc.gssd were not restarted, which means that just upgrading the packages doesn't resolve the bug: the user must issue `sudo systemctl restart nfs-utils.service`.

This happens because the nfs-utils.service is not enabled (and cannot be enabled: it's a "fake" service just meant to coordinate the several daemons necessary for NFS).

If nfs-utils.service was ever started or restarted on the machine, then the upgrade will restart it just fine.

I'm currently investigating what are the best options to address this, and will probably file a new bug.