RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2069558 - Failed to build rpm packages from nbdkit-1.30.1-2.el9.src.rpm if vhost_vsock module is loaded
Summary: Failed to build rpm packages from nbdkit-1.30.1-2.el9.src.rpm if vhost_vsock ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 9
Classification: Red Hat
Component: nbdkit
Version: 9.1
Hardware: x86_64
OS: Unspecified
low
low
Target Milestone: rc
: ---
Assignee: Virtualization Maintenance
QA Contact: mxie@redhat.com
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-03-29 07:22 UTC by mxie@redhat.com
Modified: 2022-11-15 10:07 UTC (History)
14 users (show)

Fixed In Version: nbdkit-1.30.8-1.el9
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-11-15 09:50:17 UTC
Type: Bug
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker RHELPLAN-117078 0 None None None 2022-03-29 07:24:09 UTC
Red Hat Product Errata RHBA-2022:7945 0 None None None 2022-11-15 09:50:40 UTC

Description mxie@redhat.com 2022-03-29 07:22:27 UTC 
Description of problem:
Failed to build rpm packages from nbdkit-1.30.1-2.el9.src.rpm if vhost_vsock module is loaded

Version-Release number of selected component (if applicable):
nbdkit-1.30.1-2.el9.src.rpm 

How reproducible:
100%

Steps to Reproduce:
1.Add vhost_vsock module 
# lsmod |grep vsock
vhost_vsock            24576  0
vmw_vsock_virtio_transport_common    49152  1 vhost_vsock
vhost                  57344  2 vhost_vsock,vhost_net
vsock                  53248  2 vmw_vsock_virtio_transport_common,vhost_vsock

2.Install required dependence packages to build nbdkit-1.30.1-2.el9.src.rpm
$ rpmbuild --rebuild nbdkit-1.30.1-2.el9.src.rpm 
.....
libnbd: debug: nbd1: nbd_create: opening handle
libnbd: debug: nbd1: nbd_set_uri_allow_local_file: enter: allow=true
libnbd: debug: nbd1: nbd_set_uri_allow_local_file: leave: ret=0
libnbd: debug: nbd1: nbd_set_opt_mode: enter: enable=true
libnbd: debug: nbd1: nbd_set_opt_mode: leave: ret=0
libnbd: debug: nbd1: nbd_set_full_info: enter: request=true
libnbd: debug: nbd1: nbd_set_full_info: leave: ret=0
libnbd: debug: nbd1: nbd_connect_uri: enter: uri="nbd+vsock://1:30503400"
libnbd: debug: nbd1: nbd_connect_uri: event CmdConnectSockAddr: START -> CONNECT.START
libnbd: debug: nbd1: nbd_connect_uri: transition: CONNECT.START -> DEAD
libnbd: debug: nbd1: nbd_connect_uri: leave: error="nbd_connect_uri: connect: No such device"
nbdinfo: nbd_connect_uri: connect: No such device
nbdkit: debug: ip: cleanup
nbdkit: debug: null: cleanup
nbdkit: debug: null: unload plugin
nbdkit: debug: ip: unload filter
++ _run_cleanup_hooks
++ local _status=1 _i
++ set +e
++ trap '' INT QUIT TERM EXIT ERR
++ echo ./test-ip-filter-anyvsock.sh: run cleanup hooks: exit code 1
./test-ip-filter-anyvsock.sh: run cleanup hooks: exit code 1
++ (( _i = 0 ))
++ (( _i < 0 ))
++ exit 1
FAIL test-ip-filter-anyvsock.sh (exit status: 1)
.....
+ exit 1
error: Bad exit status from /var/tmp/rpm-tmp.qtnAeb (%check)


Actual results:
As above description

Expected results:
Build rpm packages from nbdkit-1.30.1-2.el9.src.rpm successfully


Additional info:
Comment 2 Klaus Heinrich Kiwi 2022-03-29 12:58:01 UTC 
I'm going to downgrade the severity/priority of this one, as my understanding is that the pristine build (i.e., using Koji and buildroot) works fine (probably doesn't have the vsock module loaded), and while we want rpmbuild --rebuild to be somewhat resilient to environment differences, there's no guarantee that it should always work. Also, I don't think it's a customer scenario (customers are not expected to rebuild their rpms).
Comment 7 Richard W.M. Jones 2022-04-01 10:46:58 UTC 
https://listman.redhat.com/archives/libguestfs/2022-April/028545.html
Comment 8 Richard W.M. Jones 2022-04-01 12:23:52 UTC 
https://gitlab.com/nbdkit/nbdkit/-/commit/ac09992395ef0b28565a293f2c0a2855d5684d3f
Comment 15 mxie@redhat.com 2022-04-12 07:13:32 UTC 
Verify the bug with nbdkit-1.30.2-1.el9.src.rpm 

Steps:
1.Only add vhost_vsock module on server
# lsmod |grep vsock
vhost_vsock            24576  0
vmw_vsock_virtio_transport_common    49152  1 vhost_vsock
vhost                  57344  2 vhost_vsock,vhost_net
vsock                  53248  2 vmw_vsock_virtio_transport_common,vhost_vsock

2.Install required dependence packages to build nbdkit-1.30.1-2.el9.src.rpm
$ rpmbuild --rebuild nbdkit-1.30.2-1.el9.src.rpm
.....
+ exit 0


Result:
    The bug has been fixed, move it from ON_QA to VERIFIED
Comment 17 errata-xmlrpc 2022-11-15 09:50:17 UTC 
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory (nbdkit bug fix and enhancement update), and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2022:7945
Note You need to log in before you can comment on or make changes to this bug.