Comment 15 for bug 1616123

cosmic verification

First, reproducing the bug:

Cosmic packages:
ubuntu@cosmic-nfs:~$ apt-cache policy nfs-kernel-server
nfs-kernel-server:
  Installed: 1:1.3.4-2.2ubuntu3.1
  Candidate: 1:1.3.4-2.2ubuntu3.1
  Version table:
 *** 1:1.3.4-2.2ubuntu3.1 500
        500 http://br.archive.ubuntu.com/ubuntu cosmic-updates/main amd64 Packages

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

but not in used:
ubuntu@cosmic-nfs:~$ ps axw|grep svcgssd|grep -v grep
 4667 ? Ss 0:00 /usr/sbin/rpc.svcgssd

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

Right after the upgrade, the "-v" shows up in the process argument list:
...
Setting up nfs-common (1:1.3.4-2.2ubuntu3.2) ...
nfs-utils.service is a disabled or a static unit not running, not starting it.
Setting up nfs-kernel-server (1:1.3.4-2.2ubuntu3.2) ...
Processing triggers for systemd (239-7ubuntu10.13) ...
Processing triggers for man-db (2.8.4-2) ...

ubuntu@cosmic-nfs:~$ ps axw|grep svcgssd|grep -v grep
 6041 ? Ss 0:00 /usr/sbin/rpc.svcgssd -v

Cosmic verification succeeded.