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.
Created attachment 1238146[details]
/var/log/messages with NetworkManager debug enabled
Description of problem:
NetworkManager comes up on boot, but a restart of the service fails to activate bond slaves
Version-Release number of selected component (if applicable):
NetworkManager-1.0.6-31.el7_2.x86_64
kernel-3.10.0-327.41.4.el7.x86_64
How reproducible:
Always
Steps to Reproduce:
1.Boot
2.systemctl restart NetworkManager.service
Actual results:
Restart fails and networking stays down
Expected results:
Restart works and networking comes up
Additional info:
sosreport for config files, and messages file with NM debug logging, to be added as private attachments
Comment 3Beniamino Galvani
2017-01-09 08:46:46 UTC
Note that the best way to apply the changes done to a connection is by
reactivating it with:
nmcli connection up <connection name or uuid>
or using the "Activate a connection" menu of nmtui. If the changes
were made directly on ifcfg files you should tell NM to reload the
connections (before the previous command):
nmcli connection reload
Restarting NM may causes issues in some cases because NM tries to
detect which connections were previously active and this doesn't
always work correctly. We have planned to rework this area for 7.4 and
change how connections are handled upon restart, see bug 1394579.
Anyway, while the issue is reproducible on RHEL 7.2 (NM 1.0.6-31), it
doesn't happen on RHEL 7.3 (NM 1.4.0-13) as bond slaves properly come
up after the service restart.
Thank you, nmcli con reload and con down/up are working fine.
Is there any chance of getting those NM link detection patches backported to 7.2.z, or are the changes between 1.0.6 and 1.4.0 too large? If it can be done, we'll make a formal z-Stream request.
Comment 5Beniamino Galvani
2017-01-10 13:12:52 UTC
(In reply to Jamie Bainbridge from comment #4)
> Thank you, nmcli con reload and con down/up are working fine.
>
> Is there any chance of getting those NM link detection patches backported to
> 7.2.z, or are the changes between 1.0.6 and 1.4.0 too large? If it can be
> done, we'll make a formal z-Stream request.
Sorry, due to the amount of changes between 1.0.6 and 1.4.0, the
commits can't be cleanly backported and require many other patches
that are out of scope for 7.2.z and would compromise stability.
Created attachment 1238146 [details] /var/log/messages with NetworkManager debug enabled Description of problem: NetworkManager comes up on boot, but a restart of the service fails to activate bond slaves Version-Release number of selected component (if applicable): NetworkManager-1.0.6-31.el7_2.x86_64 kernel-3.10.0-327.41.4.el7.x86_64 How reproducible: Always Steps to Reproduce: 1.Boot 2.systemctl restart NetworkManager.service Actual results: Restart fails and networking stays down Expected results: Restart works and networking comes up Additional info: sosreport for config files, and messages file with NM debug logging, to be added as private attachments