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.
Exception AttributeError: "'NoneType' object has no attribute 'udev_unref'" in <bound method Context.__del__ of <pyudev.core.Context object at 0x16ef890>> ignored
DescriptionAlexander Todorov
2015-09-15 16:05:43 UTC
Description of problem:
Jenkins reports the following error below the test results, although everything seems to pass:
Exception AttributeError: "'NoneType' object has no attribute 'udev_unref'" in <bound method Context.__del__ of <pyudev.core.Context object at 0x16ef890>> ignored
I'm not sure if this is expected or we're missing a possible failure here.
(In reply to jack from comment #2)
> (In reply to David Shea from comment #1)
> >
> > *** This bug has been marked as a duplicate of bug 1252833 ***
>
> Have this bug been solved ?
No, but the message can be safely ignored.
Getting this error as well as the last thing I see before a kickstart provision fails... unfortunately I'm unable to view the ticket that was marked as a duplicate. Was hoping someone could share whatever the resolution for that one is to give me an idea of where to go?
(In reply to Matt Moldvan from comment #5)
> Never mind, sorry... turned out to be completely unrelated to anaconda.
Hi Matt Moldvan
This is driving me insane - any chance you can elaborate of how you resolved this issue?
(In reply to David Shea from comment #1)
>
> *** This bug has been marked as a duplicate of bug 1252833 ***
Except that for the rest of us, bug 1252833 is not visible and so it doesn't help us that you closed this one as a duplicate of that one.
I'm seeing this error message in 7.3. One kickstart file works if I remove the "network" line. However, I have another file that isn't fixed as readily, so I think there may be more than one bug. I'm still tracking these down.
Comment 9Samantha N. Bueno
2017-04-13 14:14:35 UTC
Apologies for the lack of response to everyone who has commented asking for more information. The issue, as noted above, has nothing to do with anaconda. This turned out to be a problem with the python-pyudev package and is being worked on presently.