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.
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
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?
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