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 1228128 - "No library named udev" error on installing RHEL-7.2-20150604.n.0 Workstation x86_64 compose
Summary: "No library named udev" error on installing RHEL-7.2-20150604.n.0 Workstatio...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: lorax
Version: 7.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Brian Lane
QA Contact: Release Test Team
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-06-04 09:31 UTC by Vadim Rutkovsky
Modified: 2015-12-01 10:43 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2015-06-05 15:24:28 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Bugzilla 1285678 0 unspecified CLOSED RHGS312 RHEL7.2 based ISO is not working. throws error like ImportError; no library named udev 2021-02-22 00:41:40 UTC

Internal Links: 1285678

Description Vadim Rutkovsky 2015-06-04 09:31:20 UTC 
Description of problem:
Anaconda crashes

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


How reproducible:
Always

Steps to Reproduce:
1. Provision a machine with RHEL-7.2-20150604.n.0 Workstation x86_64 compose
2. Check 'console.log'

Actual results:
File "/usr/lib/python2.7/site-packages/blivet/devices/__init__.py", line 22, in <module>  
    from .lib import get_device_majors, devicePathToName, deviceNameToDiskByPath, ParentList  
  File "/usr/lib/python2.7/site-packages/blivet/devices/lib.py", line 22, in <module>  
    from .. import udev  
  File "/usr/lib/python2.7/site-packages/blivet/udev.py", line 31, in <module>  
    import pyudev  
  File "/usr/lib/python2.7/site-packages/pyudev/__init__.py", line 48, in <module>  
    from pyudev.device import *  
  File "/usr/lib/python2.7/site-packages/pyudev/device.py", line 35, in <module>      
    from pyudev._libudev import libudev  
  File "/usr/lib/python2.7/site-packages/pyudev/_libudev.py", line 289, in <module>  
    libudev = load_udev_library()  
  File "/usr/lib/python2.7/site-packages/pyudev/_libudev.py", line 272, in load_udev_library  
    raise ImportError('No library named udev')  
ImportError: No library named udev

Expected results:
No crash

Additional info:
See sample task https://beaker.engineering.redhat.com/jobs/973506
Comment 1 Brian Lane 2015-06-05 15:24:28 UTC 
This is actually due to the anaconda/blivet rebase. lorax needs a few changes which will go in today as related to the rebase bug 1196721 instead of creating a new one.
Note You need to log in before you can comment on or make changes to this bug.