Comment 17 for bug 1616123

xenial verification

First, reproducing the bug:

ubuntu@xenial-nfs:~$ apt-cache policy nfs-kernel-server
nfs-kernel-server:
  Installed: 1:1.2.8-9ubuntu12.1
  Candidate: 1:1.2.8-9ubuntu12.1
  Version table:
 *** 1:1.2.8-9ubuntu12.1 500
        500 http://br.archive.ubuntu.com/ubuntu xenial-updates/main amd64 Packages

"-v" option it set:
ubuntu@xenial-nfs:~$ cat /run/sysconfig/nfs-utils
PIPEFS_MOUNTPOINT=/run/rpc_pipefs
RPCNFSDARGS=" 8"
RPCMOUNTDARGS="--manage-gids"
STATDARGS=""
RPCSVCGSSDARGS="-v"

But unused:
ubuntu@xenial-nfs:~$ ps axw|grep svcgssd|grep -v grep
 1500 ? Ss 0:00 /usr/sbin/rpc.svcgssd

With the updated packages:
ubuntu@xenial-nfs:~$ apt-cache policy nfs-kernel-server
nfs-kernel-server:
  Installed: 1:1.2.8-9ubuntu12.2
  Candidate: 1:1.2.8-9ubuntu12.2
  Version table:
 *** 1:1.2.8-9ubuntu12.2 500
        500 http://br.archive.ubuntu.com/ubuntu xenial-proposed/main amd64 Packages

It's not fixed right after the upgrade:
...
Unpacking nfs-kernel-server (1:1.2.8-9ubuntu12.2) over (1:1.2.8-9ubuntu12.1) ...
Processing triggers for ureadahead (0.100.0-19.1) ...
Processing triggers for systemd (229-4ubuntu21.21) ...
Processing triggers for man-db (2.7.5-1) ...
Setting up nfs-common (1:1.2.8-9ubuntu12.2) ...
Setting up nfs-kernel-server (1:1.2.8-9ubuntu12.2) ...
ubuntu@xenial-nfs:~$ ps axw|grep svcgssd|grep -v grep
 3022 ? Ss 0:00 /usr/sbin/rpc.svcgssd

But a restart is needed, same one used during the test:
ubuntu@xenial-nfs:~$ sudo systemctl restart nfs-config
ubuntu@xenial-nfs:~$ sudo systemctl restart nfs-server
ubuntu@xenial-nfs:~$ ps axw|grep svcgssd|grep -v grep
 3159 ? Ss 0:00 /usr/sbin/rpc.svcgssd -v

xenial verification succeeded.