Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 1630453

Summary: Facing dependency issue with python-blivet-0.61.15.71-1.el7.noarch in RHEL 7.6 Beta
Product: Red Hat Enterprise Linux 7 Reporter: gowtham <gshanmug>
Component: python-blivetAssignee: Blivet Maintenance Team <blivet-maint-list>
Status: CLOSED NOTABUG QA Contact: Release Test Team <release-test-team-automation>
Severity: urgent Docs Contact:
Priority: urgent    
Version: 7.6CC: amukherj, dahorak, gshanmug, vtrefny
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2018-09-19 13:30:59 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:    
Bug Blocks: 1628878    
Attachments:
Description Flags
Import blivet gives warning error none

Description gowtham 2018-09-18 17:13:06 UTC
Created attachment 1484441 [details]
Import blivet gives warning error

Description of problem:

In RHSC-WA(Redhat gluster storage web administration), We are using blivet package to fetch disk-related information. But we are facing some issue with RHEL 7.6 Beta version, When we try to import blivet it gives the following warning error message:
    
  ** (process:3604): WARNING **: 13:16:01.237: failed to load module nvdimm: libbd_nvdimm.so.2: cannot open shared object file: No such file or directory

In RHEL7.6 looks like it needs a package called"libblockdev-nvdimm" as a run-time dependency.

 

Version-Release number of selected component (if applicable):

OS: RHEL 7.6 beta
blivet_package: python-blivet-0.61.15.71-1.el7.noarch

How reproducible:
100% reproducible 

Steps to Reproduce:
1. Create a setup with RHEL 7.6 beta version
2. Install Blivet package python-blivet-0.61.15.71-1.el7.noarch
3. In a terminal, Python CLI try to import blivet

Actual results:
import blivet gives a run-time error

Expected results:
import blivet should happen successfully

Additional info:

Comment 3 Vojtech Trefny 2018-09-19 08:36:26 UTC
libblockdev-nvdimm is only an optional runtime depenency -- you should be able to use blivet without it as long as you don't try to configure an NVDIMM device. The warning is just a information that the nvdimm functionality is not available, the import itself finished successfully.
You can install libblockdev-nvdimm, but it shouldn't be necessary.

gowtham: Do you see some errors when running blivet functions like reset? I just did a quick manual test on latest 7.6 and everything seems to be working:

-----
$ sudo python
Python 2.7.5 (default, Sep 12 2018, 05:31:16) 
[GCC 4.8.5 20150623 (Red Hat 4.8.5-36)] on linux2
Type "help", "copyright", "credits" or "license" for more information.
>>> import blivet

** (process:13606): WARNING **: 10:15:16.510: failed to load module nvdimm: libbd_nvdimm.so.2: cannot open shared object file: No such file or directory
>>> b=blivet.Blivet()
>>> b.reset()
>>> for device in b.devices: print device.name
... 
rhel
rhel-root
rhel-swap
sr0
vda
vda1
vda2
vdb
vdb1
>>> vda = b.devicetree.getDeviceByName("vda")
>>> vda
DiskDevice instance (0x7ff41eff9b50) --
  name = vda  status = True  kids = 2 id = 7
  parents = []
  uuid = None  size = 10 GiB
  format = existing msdos disklabel
  major = 252  minor = 0  exists = True  protected = False
  sysfs path = /sys/devices/pci0000:00/0000:00:07.0/virtio2/block/vda
  target size = 10 GiB  path = /dev/vda
  format args = []  originalFormat = disklabel  removable = False
>>>
-----

Comment 4 gowtham 2018-09-19 13:30:59 UTC
I don't see any issue with reset everything is working fine. Actually, When we are parsing some output from CLI so while parsing this warning message is interrupting.

As per the above comment from blivet team, this is an expected behavior, so we have to take care of this warning message while parsing the output.

So, I am closing this issue.