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 1378809 - installation of 1.4.0 NM is possible onto 7.2 but it's not working w/o newer glib2
Summary: installation of 1.4.0 NM is possible onto 7.2 but it's not working w/o newer ...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: NetworkManager
Version: 7.3
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: Rashid Khan
QA Contact: Desktop QE
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-09-23 09:57 UTC by Vladimir Benes
Modified: 2016-11-03 19:30 UTC (History)
6 users (show)

Fixed In Version: NetworkManager-1.4.0-11.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-11-03 19:30:37 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHSA-2016:2581 0 normal SHIPPED_LIVE Low: NetworkManager security, bug fix, and enhancement update 2016-11-03 12:08:07 UTC

Description Vladimir Benes 2016-09-23 09:57:40 UTC
Description of problem:
I've clean installed RHEL7.2, then updated NM to 1.4.0-10 and rebooted. After reboot network didn't even start. I logged in via serial console and there is an error running nmcli:
nmcli: symbol lookup error: nmcli: undefined symbol: g_strv_contains

package was built on 7.3. I am not sure if such scenarios are supported.

Version-Release number of selected component (if applicable):
[root@amd-dinar-04 ~]# rpm -qa NetworkManager*
NetworkManager-1.4.0-10.el7.x86_64
NetworkManager-libnm-1.4.0-10.el7.x86_64
NetworkManager-tui-1.4.0-10.el7.x86_64
NetworkManager-config-server-1.4.0-10.el7.x86_64
NetworkManager-team-1.4.0-10.el7.x86_64

[root@amd-dinar-04 ~]# rpm -qa glib*
glibc-common-2.17-105.el7.x86_64
glib2-2.42.2-5.el7.x86_64
glib-networking-2.42.0-1.el7.x86_64

Comment 1 Vladimir Benes 2016-09-23 10:05:13 UTC
update to glib2-2.46.2-4.el7.x86_64 fixes the issue. 

Is it possible to create dynamic dependency in spec file to the version of glib you are compiling with?

Comment 4 Vladimir Benes 2016-09-23 18:30:56 UTC
Dependency to glib2-2.42.2-5.el7.x86_64 added.

Comment 6 errata-xmlrpc 2016-11-03 19:30:37 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/RHSA-2016-2581.html


Note You need to log in before you can comment on or make changes to this bug.