Your message dated Fri, 15 Nov 2024 15:49:09 +0000
with message-id <e1tbyzj-0049rs...@fasolo.debian.org>
and subject line Bug#1087516: fixed in libnvme 1.11-2
has caused the Debian Bug report #1087516,
regarding libnvme: libkeyutils support breaks usage on Debian kernel with no
TLS support
to be marked as done.
This means that you claim that the problem has been dealt with.
If this is not the case it is now your responsibility to reopen the
Bug report if necessary, and/or fix the problem forthwith.
(NB: If you are a system administrator and have no idea what this
message is talking about, this may indicate a serious mail system
misconfiguration somewhere. Please contact ow...@bugs.debian.org
immediately.)
--
1087516: https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=1087516
Debian Bug Tracking System
Contact ow...@bugs.debian.org with problems
--- Begin Message ---
Source: libnvme
Version: 1.11-1
Severity: grave
Justification: breaks autopkgtest of another package
Forwarded: https://github.com/linux-nvme/nvme-cli/issues/2573
Dear Maintainer(s),
libnvme since version 2.11 does not work if it is built with keyutils
support, but runs on a kernel without CONFIG_NVME_TCP_TLS and
CONFIG_NVME_HOST_AUTH, as it unconditionally expects the .nvme keyring
to be available, and hard fails otherwise.
https://github.com/linux-nvme/libnvme/blob/f1ddb968ce03a67a96e3f9069e9b758532cf67b9/src/nvme/linux.c#L1551
# nvme connect-all -t tcp -a 127.0.0.1 -s 16858
--hostid=158f4d7d-6759-499e-b260-b152e49fa9a2
Failed to set keyring
failed to add controller, error Required key not available
On Debian the kernel does not enable the required kconfigs, so the
command is currently broken as the .nvme keyring doesn't exist.
This is now breaking src:systemd autopkgtest, which has a test for an
nvme tcp server that uses nvme-cli, hence the severity:
https://ci.debian.net/packages/s/systemd/testing/amd64/
Unfortunately there was no direct dependency in autopkgtest so the test
that was previously working wasn't rerun before nvme-cli migrated to
testing, I've fixed that now so that future regressions will be caught
by debci before migration.
I've also reported this upstream:
https://github.com/linux-nvme/nvme-cli/issues/2573
Ideally the userspace tool should not fail hard when the kernel doesn't
enable the required functionality, especially when the invocation
doesn't explicitly enable any tls option, but that will require
upstream to fix it.
--- End Message ---
--- Begin Message ---
Source: libnvme
Source-Version: 1.11-2
Done: Daniel Baumann <daniel.baum...@progress-linux.org>
We believe that the bug you reported is fixed in the latest version of
libnvme, which is due to be installed in the Debian FTP archive.
A summary of the changes between this version and the previous one is
attached.
Thank you for reporting the bug, which will now be closed. If you
have further comments please address them to 1087...@bugs.debian.org,
and the maintainer will reopen the bug report if appropriate.
Debian distribution maintenance software
pp.
Daniel Baumann <daniel.baum...@progress-linux.org> (supplier of updated libnvme
package)
(This message was generated automatically at their request; if you
believe that there is a problem with it please contact the archive
administrators by mailing ftpmas...@ftp-master.debian.org)
-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA512
Format: 1.8
Date: Fri, 15 Nov 2024 16:29:56 +0100
Source: libnvme
Architecture: source
Version: 1.11-2
Distribution: sid
Urgency: medium
Maintainer: Daniel Baumann <daniel.baum...@progress-linux.org>
Changed-By: Daniel Baumann <daniel.baum...@progress-linux.org>
Closes: 1087516
Changes:
libnvme (1.11-2) sid; urgency=medium
.
* Uploading to sid.
* Adding patch from upstream to handle unavailable keyring gracefully
(Closes: #1087516).
Checksums-Sha1:
5eaad82ca9d0fd0118482597d278ba0b8353a34d 2254 libnvme_1.11-2.dsc
7e1fef2b855974b99ba3869f2ae4bafab43a49db 8820 libnvme_1.11-2.debian.tar.xz
824953ef13348361af396d6201f0d77646213ed8 9583 libnvme_1.11-2_amd64.buildinfo
Checksums-Sha256:
bc3a598d1c8c67c0d71ac9ffeb0b4f78be91990dd2d6c82640260ad2a42bd8f6 2254
libnvme_1.11-2.dsc
bffe433aadd91f87b43607f77c24dc6dc71b105b28b268aedf88086b021e9589 8820
libnvme_1.11-2.debian.tar.xz
309940f970bce506d853dd4a967e5d28d9fe358ba0e1b75f520abb593e9ee9b5 9583
libnvme_1.11-2_amd64.buildinfo
Files:
beda3e85dda3f174d5e8e50258c13309 2254 libs optional libnvme_1.11-2.dsc
9b6901ac07ef7552fcd60c4ff4a23edd 8820 libs optional
libnvme_1.11-2.debian.tar.xz
de7625464e5df82c111d6aa2b218f44f 9583 libs optional
libnvme_1.11-2_amd64.buildinfo
-----BEGIN PGP SIGNATURE-----
iQIzBAEBCgAdFiEEgTbtJcfWfpLHSkKSVc8b+YaruccFAmc3aV4ACgkQVc8b+Yar
ucehCg//dovGpgSPIgAdkb3/swQCFlD1DGotqdp/tbIMJ8iPLnQugJtY7XurbSV1
mmY4ZcsPiMtNBC2euzpPM4LPHWKpQImPqDno3ml+tX3XebXjvXZ+WY+8MmT2vIAp
G6tTLzMyL1UsyxLP8C/qT/FkXp8NhTeRiwxoAaUrWiLAS+UN4VB7nTp7VvgGit6d
JjW7BKyn8Xq3NO2WToFeCKokrXietWHLrkEriCuFgAkT42KwTXGpai2a9uXfqX99
o5WEeaLdUFfr/o1/5kkFaaM33Mp0GMlnN3810i/ze0mescNoWX4GlW3LIMVdzfcg
KXg/XTQcJhYgAhzpmc8XCsv0l7Rf+V+7Oyj5mLmxQMVin9oYnnzqzl22fGAx5WKF
NBFbgNyodsqfH1W+n0Xr9TWZzhOsVLLPdTl5dZIFnXxZyPwhE+KIaAXoKZ/kEiCK
GxVugmgBeYdmwuAhT0m30Mrh+KHwiSZtUlHPtvnmfuWpuvuEPaMpEcoTGn+x3A9K
0RUD3Kl91sw65Z1T8RD5BHr9P/68IKLbpwJ1gEUz/D+6kP+cyrBoKz5xmmQEIhwO
grSsrcHYRXL9hTY70deP4zYmuAzfWvhL3M80PN9tXFA3xVx7BCWqC0MT6sh67OzS
rLo0Zqtw/aMVHD3VLO/BdY5GrbJrsSAnG+FL6fmhir/MVKdjKcU=
=GwgC
-----END PGP SIGNATURE-----
pgpYTejOm1ahP.pgp
Description: PGP signature
--- End Message ---