focal, with modified /etc/nvme/hostnqn but not modified hostid:
root@lp1867366-f:~# dpkg -l | grep nvme-cli
ii nvme-cli 1.9-1 amd64 userspace tooling to control NVMe drives
root@lp1867366-f:~# grep . /etc/nvme/host*
/etc/nvme/hostid:9ce77162-5a3e-439b-a73f-cdf2449521b6
/etc/nvme/hostnqn:I'm a modified hostnqn file!
root@lp1867366-f:~# apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
nvme-cli
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 283 kB of archives.
After this operation, 3072 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://archive.ubuntu.com/ubuntu focal-proposed/universe amd64 nvme-cli amd64 1.9-1ubuntu0.1 [283 kB]
Fetched 283 kB in 1s (406 kB/s)
(Reading database ... 47296 files and directories currently installed.)
Preparing to unpack .../nvme-cli_1.9-1ubuntu0.1_amd64.deb ...
Unpacking nvme-cli (1.9-1ubuntu0.1) over (1.9-1) ...
Setting up nvme-cli (1.9-1ubuntu0.1) ...
WARNING: /etc/nvme/hostid is not unique, you should regenerate it (LP:#1867366)
Processing triggers for man-db (2.9.1-1) ...
root@lp1867366-f:~# dpkg -l | grep nvme-cli
ii nvme-cli 1.9-1ubuntu0.1 amd64 userspace tooling to control NVMe drives
root@lp1867366-f:~# grep . /etc/nvme/host*
/etc/nvme/hostid:9ce77162-5a3e-439b-a73f-cdf2449521b6
/etc/nvme/hostnqn:I'm a modified hostnqn file!
note: as outlined in comment 17, since the hostnqn has been modified, it's possible the system is in use as a nvmeof target, so the hostid and hostnqn files are left as-is without modification, but a warning is printed about the hostid not being a unique value.
focal, with modified /etc/nvme/hostnqn but not modified hostid:
root@lp1867366-f:~# dpkg -l | grep nvme-cli hostid: 9ce77162- 5a3e-439b- a73f-cdf2449521 b6 hostnqn: I'm a modified hostnqn file! archive. ubuntu. com/ubuntu focal-proposed/ universe amd64 nvme-cli amd64 1.9-1ubuntu0.1 [283 kB] cli_1.9- 1ubuntu0. 1_amd64. deb ... hostid: 9ce77162- 5a3e-439b- a73f-cdf2449521 b6 hostnqn: I'm a modified hostnqn file!
ii nvme-cli 1.9-1 amd64 userspace tooling to control NVMe drives
root@lp1867366-f:~# grep . /etc/nvme/host*
/etc/nvme/
/etc/nvme/
root@lp1867366-f:~# apt upgrade
Reading package lists... Done
Building dependency tree
Reading state information... Done
Calculating upgrade... Done
The following packages will be upgraded:
nvme-cli
1 upgraded, 0 newly installed, 0 to remove and 0 not upgraded.
Need to get 283 kB of archives.
After this operation, 3072 B of additional disk space will be used.
Do you want to continue? [Y/n] y
Get:1 http://
Fetched 283 kB in 1s (406 kB/s)
(Reading database ... 47296 files and directories currently installed.)
Preparing to unpack .../nvme-
Unpacking nvme-cli (1.9-1ubuntu0.1) over (1.9-1) ...
Setting up nvme-cli (1.9-1ubuntu0.1) ...
WARNING: /etc/nvme/hostid is not unique, you should regenerate it (LP:#1867366)
Processing triggers for man-db (2.9.1-1) ...
root@lp1867366-f:~# dpkg -l | grep nvme-cli
ii nvme-cli 1.9-1ubuntu0.1 amd64 userspace tooling to control NVMe drives
root@lp1867366-f:~# grep . /etc/nvme/host*
/etc/nvme/
/etc/nvme/
note: as outlined in comment 17, since the hostnqn has been modified, it's possible the system is in use as a nvmeof target, so the hostid and hostnqn files are left as-is without modification, but a warning is printed about the hostid not being a unique value.