-
Bug
-
Resolution: Unresolved
-
Normal
-
None
-
rhel-9.3.0
-
None
-
Moderate
-
rhel-sst-virtualization
-
ssg_virtualization
-
5
-
False
-
-
None
-
None
-
None
-
None
-
If docs needed, set a value
-
-
Unspecified
-
None
Description of problem:
On RHEL-9.3.0-20230405.0 compose, the 'virt-builder --list -v -x' command fails with the next error:
command line: virt-builder --list -v -x
/usr/bin/gpg2 --help >/dev/null 2>&1
curl --help >/dev/null 2>&1
virt-resize --help >/dev/null 2>&1
trying to read /etc/virt-builder/repos.d/libguestfs.conf
read 2 sources
trying to read /etc/virt-builder/repos.d/opensuse.conf
read 0 sources
/usr/bin/gpg2 --homedir /tmp/virt-builder.KPm6PU/vb.gpghome.qtIhGF --list-keys
gpg: keybox '/tmp/virt-builder.KPm6PU/vb.gpghome.qtIhGF/pubring.kbx' created
gpg: /tmp/virt-builder.KPm6PU/vb.gpghome.qtIhGF/trustdb.gpg: trustdb created
/usr/bin/gpg2 --homedir /tmp/virt-builder.KPm6PU/vb.gpghome.qtIhGF --status-file '/tmp/virt-builder.KPm6PU/vbstatf93317.txt' --import '/etc/virt-builder/repos.d/libguestfs.gpg'
gpg: Note: signatures using the SHA1 algorithm are rejected
gpg: key 91738F73E1B768A0: 3 bad signatures
gpg: key 91738F73E1B768A0: new key but contains no user ID - skipped
gpg: Total number processed: 1
gpg: w/o user IDs: 1
/usr/bin/gpg2 --homedir /tmp/virt-builder.KPm6PU/vb.gpghome.qtIhGF --trusted-key '' --list-keys
gpg: '' is not a valid long keyID
virt-builder: error: GPG failure: could not trust the imported key
Use the ā-vā option and look for earlier error messages.
rm -rf – '/tmp/virt-builder.KPm6PU'
Version-Release number of selected component (if applicable):
guestfs-tools-1.48.2-8.el9.x86_64
kernel-5.14.0-295.el9.x86_64
gnupg2-2.3.3-3.el9.x86_64
How reproducible:
100% (baremetal or VM in beaker)
Steps:
1.
2.
3.
Actual results:
As above
Expected results:
virt-builder works fine as usual.
Additional info:
1. Our automation hit this issue on RHEL-9.3.0-20230403.57, RHEL-9.3.0-20230404.31, and RHEL-9.3.0-20230405.0 composes with beaker baremetal.
2. Can not reproduce this issue on PSI OpenStack env.
3. No such issue on RHEL8.9
- external trackers