| 2020-03-13 16:12:29 |
Jennifer Duong |
bug |
|
|
added bug |
| 2020-03-13 16:15:36 |
Jennifer Duong |
bug |
|
|
added subscriber NetApp HSG Interoperability |
| 2020-03-24 21:29:50 |
Jennifer Duong |
nvme-cli (Ubuntu): status |
New |
Confirmed |
|
| 2020-08-28 20:46:23 |
Dan Streetman |
nominated for series |
|
Ubuntu Groovy |
|
| 2020-08-28 20:46:23 |
Dan Streetman |
bug task added |
|
nvme-cli (Ubuntu Groovy) |
|
| 2020-08-28 20:46:23 |
Dan Streetman |
nominated for series |
|
Ubuntu Focal |
|
| 2020-08-28 20:46:23 |
Dan Streetman |
bug task added |
|
nvme-cli (Ubuntu Focal) |
|
| 2020-08-28 20:46:23 |
Dan Streetman |
nominated for series |
|
Ubuntu Bionic |
|
| 2020-08-28 20:46:23 |
Dan Streetman |
bug task added |
|
nvme-cli (Ubuntu Bionic) |
|
| 2020-08-28 20:46:36 |
Dan Streetman |
nvme-cli (Ubuntu Focal): assignee |
|
Dan Streetman (ddstreet) |
|
| 2020-08-28 20:46:40 |
Dan Streetman |
nvme-cli (Ubuntu Groovy): assignee |
|
Dan Streetman (ddstreet) |
|
| 2020-08-28 20:46:42 |
Dan Streetman |
nvme-cli (Ubuntu Bionic): assignee |
|
Dan Streetman (ddstreet) |
|
| 2020-08-28 20:46:49 |
Dan Streetman |
nvme-cli (Ubuntu Groovy): status |
Confirmed |
In Progress |
|
| 2020-08-28 20:46:49 |
Dan Streetman |
nvme-cli (Ubuntu Focal): importance |
Undecided |
Low |
|
| 2020-08-28 20:46:50 |
Dan Streetman |
nvme-cli (Ubuntu Focal): status |
New |
In Progress |
|
| 2020-08-28 20:46:54 |
Dan Streetman |
nvme-cli (Ubuntu Bionic): importance |
Undecided |
Low |
|
| 2020-08-28 20:46:55 |
Dan Streetman |
nvme-cli (Ubuntu Bionic): status |
New |
In Progress |
|
| 2020-08-28 20:54:07 |
Dan Streetman |
nvme-cli (Ubuntu Groovy): importance |
Undecided |
Low |
|
| 2020-08-28 21:04:29 |
Dan Streetman |
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 |
[impact]
"nvme gen-hostnqn" does not work, leading to no content in /etc/nvme/hostnqn
[test case]
ddstreet@thorin:~$ cat /etc/nvme/hostnqn
ddstreet@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
[scope]
xenial does not include the gen-hostnqn command, so this is needed only for bionic and later
[other info]
to fix this in debian, this bug is open:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969183
[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 |
|
| 2020-08-28 21:04:38 |
Dan Streetman |
bug watch added |
|
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969183 |
|
| 2020-08-28 21:04:38 |
Dan Streetman |
bug task added |
|
nvme-cli (Debian) |
|
| 2020-08-28 21:51:53 |
Dan Streetman |
description |
[impact]
"nvme gen-hostnqn" does not work, leading to no content in /etc/nvme/hostnqn
[test case]
ddstreet@thorin:~$ cat /etc/nvme/hostnqn
ddstreet@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
[scope]
xenial does not include the gen-hostnqn command, so this is needed only for bionic and later
[other info]
to fix this in debian, this bug is open:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969183
[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 |
[impact]
"nvme gen-hostnqn" does not work, leading to no content in /etc/nvme/hostnqn
[test case]
ddstreet@thorin:~$ cat /etc/nvme/hostnqn
ddstreet@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
[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.
[other info]
to fix this in debian, this bug is open:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969183
[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 |
|
| 2020-08-31 18:44:23 |
Dan Streetman |
description |
[impact]
"nvme gen-hostnqn" does not work, leading to no content in /etc/nvme/hostnqn
[test case]
ddstreet@thorin:~$ cat /etc/nvme/hostnqn
ddstreet@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
[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.
[other info]
to fix this in debian, this bug is open:
https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=969183
[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 |
[impact]
"nvme gen-hostnqn" does not work, leading to no content in /etc/nvme/hostnqn
[test case]
ddstreet@thorin:~$ cat /etc/nvme/hostnqn
ddstreet@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
[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.
[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 |
|
| 2020-09-01 04:38:06 |
Launchpad Janitor |
nvme-cli (Ubuntu Groovy): status |
In Progress |
Fix Released |
|
| 2020-09-01 14:50:37 |
Dan Streetman |
description |
[impact]
"nvme gen-hostnqn" does not work, leading to no content in /etc/nvme/hostnqn
[test case]
ddstreet@thorin:~$ cat /etc/nvme/hostnqn
ddstreet@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
[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.
[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 |
[impact]
"nvme gen-hostnqn" does not work, leading to no content in /etc/nvme/hostnqn
[test case]
ddstreet@thorin:~$ cat /etc/nvme/hostnqn
ddstreet@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
[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.
[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 |
|
| 2020-09-01 14:51:02 |
Dan Streetman |
bug |
|
|
added subscriber Ubuntu Storage Interest |
| 2020-09-01 14:51:19 |
Dan Streetman |
bug |
|
|
added subscriber Rafael David Tinoco |
| 2020-09-01 19:22:23 |
Brian Murray |
nvme-cli (Ubuntu Focal): status |
In Progress |
Incomplete |
|
| 2020-09-02 18:14:54 |
Rafael David Tinoco |
bug |
|
|
added subscriber Ubuntu Server |
| 2020-09-02 19:55:12 |
Rafael David Tinoco |
nvme-cli (Ubuntu Focal): status |
Incomplete |
Confirmed |
|
| 2020-09-02 19:55:16 |
Rafael David Tinoco |
nvme-cli (Ubuntu Bionic): status |
In Progress |
Confirmed |
|
| 2020-09-04 14:40:30 |
Dan Streetman |
description |
[impact]
"nvme gen-hostnqn" does not work, leading to no content in /etc/nvme/hostnqn
[test case]
ddstreet@thorin:~$ cat /etc/nvme/hostnqn
ddstreet@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
[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.
[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 |
[impact]
"nvme gen-hostnqn" does not work, leading to no content in /etc/nvme/hostnqn
[test case]
ddstreet@thorin:~$ cat /etc/nvme/hostnqn
ddstreet@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 |
|
| 2020-09-04 14:41:43 |
Dan Streetman |
nvme-cli (Ubuntu Focal): status |
Confirmed |
In Progress |
|
| 2020-09-04 14:41:45 |
Dan Streetman |
nvme-cli (Ubuntu Bionic): status |
Confirmed |
In Progress |
|
| 2020-09-04 14:46:19 |
Dan Streetman |
description |
[impact]
"nvme gen-hostnqn" does not work, leading to no content in /etc/nvme/hostnqn
[test case]
ddstreet@thorin:~$ cat /etc/nvme/hostnqn
ddstreet@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 |
[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@thorin:~$ cat /etc/nvme/hostnqn
ddstreet@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 |
|
| 2020-09-04 14:47:56 |
Dan Streetman |
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]
ddstreet@thorin:~$ cat /etc/nvme/hostnqn
ddstreet@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 |
[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 |
|
| 2020-09-07 02:29:33 |
Dan Streetman |
bug |
|
|
added subscriber Dan Streetman |
| 2020-09-08 18:44:01 |
Brian Murray |
nvme-cli (Ubuntu Focal): status |
In Progress |
Fix Committed |
|
| 2020-09-08 18:44:03 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2020-09-08 18:44:06 |
Brian Murray |
bug |
|
|
added subscriber SRU Verification |
| 2020-09-08 18:44:12 |
Brian Murray |
tags |
amd64 apport-bug focal |
amd64 apport-bug focal verification-needed verification-needed-focal |
|
| 2020-09-18 18:43:39 |
Dan Streetman |
tags |
amd64 apport-bug focal verification-needed verification-needed-focal |
amd64 apport-bug focal verification-done verification-done-focal |
|
| 2020-09-22 16:07:24 |
Launchpad Janitor |
nvme-cli (Ubuntu Focal): status |
Fix Committed |
Fix Released |
|
| 2020-09-22 16:07:28 |
Brian Murray |
removed subscriber Ubuntu Stable Release Updates Team |
|
|
|
| 2020-10-21 13:58:07 |
Matt Schulte |
bug |
|
|
added subscriber Matt Schulte |
| 2020-11-10 19:14:50 |
Brian Murray |
nvme-cli (Ubuntu Bionic): status |
In Progress |
Fix Committed |
|
| 2020-11-10 19:14:53 |
Brian Murray |
bug |
|
|
added subscriber Ubuntu Stable Release Updates Team |
| 2020-11-10 19:15:00 |
Brian Murray |
tags |
amd64 apport-bug focal verification-done verification-done-focal |
amd64 apport-bug focal verification-done-focal verification-needed verification-needed-bionic |
|
| 2020-11-18 18:55:03 |
Dan Streetman |
tags |
amd64 apport-bug focal verification-done-focal verification-needed verification-needed-bionic |
amd64 apport-bug focal verification-done verification-done-bionic verification-done-focal |
|
| 2020-11-23 11:46:24 |
Launchpad Janitor |
nvme-cli (Ubuntu Bionic): status |
Fix Committed |
Fix Released |
|
| 2021-03-02 07:01:56 |
Bug Watch Updater |
nvme-cli (Debian): status |
Unknown |
Fix Released |
|
