Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 1670053

Summary: python plugin incorrect initialization of built in "nbdkit" module
Product: Red Hat Enterprise Linux Advanced Virtualization Reporter: Richard W.M. Jones <rjones>
Component: nbdkitAssignee: Libvirt Maintainers <libvirt-maint>
Status: CLOSED DUPLICATE QA Contact: Virtualization Bugs <virt-bugs>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 8.1CC: extras-qa, hkario, jsuchane, juzhou, knoel, mxie, mzhan, ptoscano, rjones, tburke, tzheng, xiaodwan, zili
Target Milestone: rc   
Target Release: 8.0   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: 1669891 Environment:
Last Closed: 2019-08-27 10:50:38 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1669891    
Bug Blocks:    

Description Richard W.M. Jones 2019-01-28 13:56:28 UTC
+++ This bug was initially created as a clone of Bug #1669891 +++

Description of problem:

nbdkit python plugin (both Python 2 & Python 3) was found to
be initializing the built in nbdkit API module incorrectly.  A
simple test which demonstrates this is:

$ echo "import nbdkit" > test.py
$ nbdkit python3 test.py
Traceback (most recent call last):
  File "test.py", line 1, in <module>
    import nbdkit
ModuleNotFoundError: No module named 'nbdkit'
nbdkit: error: test.py: error running this script

NOTE you will only see the error with a very recent version
of Python 3.7.  Earlier versions of Python don't fail, but
since we are using the Python API incorrectly they could
begin to fail at any time.

This is fixed upstream in:

https://github.com/libguestfs/nbdkit/commit/6e756abe3db120f67bd789e3eb2f5a0449b8dab1
https://github.com/libguestfs/nbdkit/commit/308092dfaf191e9ef59eeaa3db81f3b65a3bb31f

Comment 2 Richard W.M. Jones 2019-08-27 10:50:38 UTC
This is another one where I incorrectly filed it against RHEL 8 instead
of AV.  This has been fixed in AV by rebasing, so I think the easiest
thing here is to simply mark this as a duplicate of the rebase bug.

*** This bug has been marked as a duplicate of bug 1705238 ***