[Bug 1867366] Re: hostnqn fails to automatically generate after installing nvme-cli
Dan Streetman
1867366 at bugs.launchpad.net
Fri Sep 4 14:40:30 UTC 2020
** Description changed:
[impact]
"nvme gen-hostnqn" does not work, leading to no content in
/etc/nvme/hostnqn
[test case]
ddstreet at thorin:~$ cat /etc/nvme/hostnqn
ddstreet at thorin:~$ nvme gen-hostnqn
"gen-hostnqn" not supported. Install lib uuid and rebuild.
[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, it regenerates
- it (so the host has a unique generated value). Anyone using the old
- hardcoded hostid will be affected by this
+ 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.
- note that in bionic, the 'gen-hostnqn' command exists, but the
- /etc/nvme/hostnqn file is not provided by the package.
+ 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://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969183
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969340
[original description]
hostnqn fails to automatically generate after installing nvme-cli
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nvme-cli 1.9-1
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
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_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: nvme-cli
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.nvme.hostnqn: [modified]
mtime.conffile..etc.nvme.hostnqn: 2020-03-06T11:27:08.674276
** Changed in: nvme-cli (Ubuntu Focal)
Status: Confirmed => In Progress
** Changed in: nvme-cli (Ubuntu Bionic)
Status: Confirmed => In Progress
** Description changed:
[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]
ddstreet at thorin:~$ cat /etc/nvme/hostnqn
ddstreet at thorin:~$ nvme gen-hostnqn
"gen-hostnqn" not supported. Install lib uuid and rebuild.
[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://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969183
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969340
[original description]
hostnqn fails to automatically generate after installing nvme-cli
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nvme-cli 1.9-1
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
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_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: nvme-cli
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.nvme.hostnqn: [modified]
mtime.conffile..etc.nvme.hostnqn: 2020-03-06T11:27:08.674276
** Description changed:
[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]
- ddstreet at thorin:~$ cat /etc/nvme/hostnqn
+ hostnqn tests:
- ddstreet at thorin:~$ nvme gen-hostnqn
+ $ 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-5a3e-439b-a73f-cdf2449521b6
+
+ (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://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969183
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969340
[original description]
hostnqn fails to automatically generate after installing nvme-cli
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nvme-cli 1.9-1
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
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_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: nvme-cli
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.nvme.hostnqn: [modified]
mtime.conffile..etc.nvme.hostnqn: 2020-03-06T11:27:08.674276
--
You received this bug notification because you are a member of Ubuntu
Foundations Bugs, which is subscribed to nvme-cli in Ubuntu.
https://bugs.launchpad.net/bugs/1867366
Title:
hostnqn fails to automatically generate after installing nvme-cli
Status in nvme-cli package in Ubuntu:
Fix Released
Status in nvme-cli source package in Bionic:
In Progress
Status in nvme-cli source package in Focal:
In Progress
Status in nvme-cli source package in Groovy:
Fix Released
Status in nvme-cli package in Debian:
Unknown
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-5a3e-439b-a73f-cdf2449521b6
(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://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969183
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969340
[original description]
hostnqn fails to automatically generate after installing nvme-cli
ProblemType: Bug
DistroRelease: Ubuntu 20.04
Package: nvme-cli 1.9-1
ProcVersionSignature: Ubuntu 5.4.0-9.12-generic 5.4.3
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_DIR=<set>
LANG=en_US.UTF-8
SHELL=/bin/bash
SourcePackage: nvme-cli
UpgradeStatus: No upgrade log present (probably fresh install)
modified.conffile..etc.nvme.hostnqn: [modified]
mtime.conffile..etc.nvme.hostnqn: 2020-03-06T11:27:08.674276
To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/nvme-cli/+bug/1867366/+subscriptions
More information about the foundations-bugs
mailing list