hostnqn fails to automatically generate after installing nvme-cli
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
nvme-cli (Debian) |
Fix Released
|
Unknown
|
|||
nvme-cli (Ubuntu) |
Fix Released
|
Low
|
Dan Streetman | ||
Bionic |
Fix Released
|
Low
|
Dan Streetman | ||
Focal |
Fix Released
|
Low
|
Dan Streetman | ||
Groovy |
Fix Released
|
Low
|
Dan Streetman |
Bug Description
[impact]
"nvme gen-hostnqn" does not work, leading to no content in /etc/nvme/hostnqn
also, /etc/nvme/hostid is generated at build time instead of install time, leading to a hardcoded value for all systems, while the file is supposed to contain a unique value (uuid) for the system
[test case]
hostnqn tests:
$ cat /etc/nvme/hostnqn
$ nvme gen-hostnqn
"gen-hostnqn" not supported. Install lib uuid and rebuild.
hostid test for unique value:
$ cat /etc/nvme/hostid
9ce77162-
(that specific uuid is hardcoded into the nvme-cli 1.9-1 package)
[regression potential]
any regression would likely involve a failure of nvme to interact with nvmeof devices, or for other systems connecting to this nvme fabric target to encounter errors
also, the upload for Focal includes a postinst check for the hardcoded hostid value (from the 1.9-1 package), and if it's found *and* the hostnqn is not set (meaning the system has not been setup yet), it regenerates it (so the host has a unique generated value). Any regression in this area would likely involve the same issues as above with NVMEoF problems, either in connecting or operating the system as a target.
see comments 11-17 for more analysis of the issue and regression potential.
[scope]
xenial does not include the gen-hostnqn command, so this is needed only for bionic and later.
in bionic, the 'gen-hostnqn' command exists, but the /etc/nvme/hostnqn file is not (yet) provided by the package, however per recommendation in comment 17, the postinst script is being added to the bionic upload, so the hostid and hostnqn files will be generated at package installation.
[other info]
to fix this in debian:
https:/
https:/
[original description]
hostnqn fails to automatically generate after installing nvme-cli
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nvme-cli 1.9-1
ProcVersionSign
Uname: Linux 5.4.0-9-generic x86_64
ApportVersion: 2.20.11-0ubuntu18
Architecture: amd64
Date: Fri Mar 6 14:09:20 2020
Dependencies:
gcc-9-base 9.2.1-21ubuntu1
libc6 2.30-0ubuntu3
libgcc1 1:9.2.1-21ubuntu1
libidn2-0 2.2.0-2
libunistring2 0.9.10-2
InstallationDate: Installed on 2020-03-05 (0 days ago)
InstallationMedia: Ubuntu-Server 20.04 LTS "Focal Fossa" - Alpha amd64 (20200124)
ProcEnviron:
TERM=xterm
PATH=(custom, no user)
XDG_RUNTIME_
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: nvme-cli
UpgradeStatus: No upgrade log present (probably fresh install)
modified.
mtime.conffile.
Changed in nvme-cli (Ubuntu Focal): | |
assignee: | nobody → Dan Streetman (ddstreet) |
Changed in nvme-cli (Ubuntu Groovy): | |
assignee: | nobody → Dan Streetman (ddstreet) |
Changed in nvme-cli (Ubuntu Bionic): | |
assignee: | nobody → Dan Streetman (ddstreet) |
Changed in nvme-cli (Ubuntu Groovy): | |
status: | Confirmed → In Progress |
Changed in nvme-cli (Ubuntu Focal): | |
importance: | Undecided → Low |
status: | New → In Progress |
Changed in nvme-cli (Ubuntu Bionic): | |
importance: | Undecided → Low |
status: | New → In Progress |
Changed in nvme-cli (Ubuntu Groovy): | |
importance: | Undecided → Low |
description: | updated |
description: | updated |
description: | updated |
description: | updated |
Changed in nvme-cli (Ubuntu Focal): | |
status: | Incomplete → Confirmed |
Changed in nvme-cli (Ubuntu Bionic): | |
status: | In Progress → Confirmed |
description: | updated |
Changed in nvme-cli (Ubuntu Focal): | |
status: | Confirmed → In Progress |
Changed in nvme-cli (Ubuntu Bionic): | |
status: | Confirmed → In Progress |
description: | updated |
description: | updated |
tags: |
added: verification-done verification-done-bionic removed: verification-needed verification-needed-bionic |
Changed in nvme-cli (Debian): | |
status: | Unknown → Fix Released |
Has anyone had a chance to look at this?