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 1268767 - virsh start failures due to OLD libnl3 version
Summary: virsh start failures due to OLD libnl3 version
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: libnl3
Version: 7.1
Hardware: All
OS: Linux
urgent
medium
Target Milestone: rc
: ---
Assignee: Rashid Khan
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On: 1249158
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-10-05 08:19 UTC by Jan Kurik
Modified: 2019-09-12 09:02 UTC (History)
7 users (show)

Fixed In Version: libnl3-3.2.21-9.el7_1
Doc Type: Bug Fix
Doc Text:
Previously, connecting to a Netlink socket could fail due to a local port being already in use. There were also restrictions about the number of socket instances that could be created. A patch has been applied to fix this bug, and the connection can now be established as expected.
Clone Of: 1249158
Environment:
Last Closed: 2015-11-04 14:38:48 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:1963 0 normal SHIPPED_LIVE libnl3 bug fix update 2015-11-04 19:38:24 UTC

Description Jan Kurik 2015-10-05 08:19:52 UTC 
This bug has been copied from bug #1249158 and has been proposed
to be backported to 7.1 z-stream (EUS).
Comment 5 Thomas Haller 2015-10-05 10:27:05 UTC 
The test script from https://bugzilla.redhat.com/show_bug.cgi?id=1249158#c4 can be used to verify the fix.
Comment 8 errata-xmlrpc 2015-11-04 14:38:48 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, 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://rhn.redhat.com/errata/RHBA-2015-1963.html
Note You need to log in before you can comment on or make changes to this bug.