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 1220374 - teaming is not working after systemctl restart network
Summary: teaming is not working after systemctl restart network
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: initscripts
Version: 7.0
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: rc
: ---
Assignee: initscripts Maintenance Team
QA Contact: Jan Ščotka
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2015-05-11 12:31 UTC by Marek Grac
Modified: 2016-11-25 12:59 UTC (History)
2 users (show)

Fixed In Version: initscripts-9.49.25-1.el7
Doc Type: Bug Fix
Doc Text:
Fix: Now during restart of network initscripts we are also telling NM to refresh its configuration (because network initscripts usually does not handle the devices, NM does).
Clone Of:
Environment:
Last Closed: 2015-11-19 11:23:51 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2015:2134 0 normal SHIPPED_LIVE initscripts bug fix update 2015-11-19 10:18:39 UTC

Description Marek Grac 2015-05-11 12:31:54 UTC 
Summary:
It is required to run "/usr/bin/systemctl restart network.service" twice to has working teaming after appropriate ifcfg- where changed. 

Description:
Let have a system with clean installation with three network cards:
* eth0 - network A
* eth1, eth2 - network B

previous config files are all DHCP based (created by kickstart)

minimal config for ifcfg-eth1/2
TEAM_MASTER=team0
DEVICETYPE=teamport
HWADDR=52:54:00:01:00:4b
ONBOOT=yes
BOOTPROTO=none

master config:
DEVICE=team0
NAME=team0
DEVICETYPE=team
ONBOOT=yes
BOOTPROTO=dhcp
TEAM_CONFIG='{"runner": {"name": "activebackup"}, "hwaddr" : "52:54:00:01:00:4b"}'
IPV6INIT=NO

Let's do a restart:
Job for network.service failed. See 'systemctl status network.service' and 'journalctl -xn' for details.

2nd attempt ends with success

only useful information found in log is:
May 11 14:18:27 virt-076.cluster-qe.lab.eng.brq.redhat.com network[2980]: RTNETLINK answers: File exists

several times. 

Expected result:
teaming will work after first restart of network settings.
Comment 1 Lukáš Nykrýn 2015-05-11 12:38:41 UTC 
Was the network service running (from systemd poit-of-view), before the first restart? 

Can you try following commands instead of systemctl restart?

export SYSTEMCTL_SKIP_REDIRECT=1
service network restart
Comment 3 Marek Grac 2015-05-11 13:20:31 UTC 
@Lukáš:

yes, network is running at the start - all devices has IP address obtained from DHCP

output with yours setting:
eth0 is not part of teaming (dhcp)
eth1/2 previously single (dhcp) -> now teaming

device exists but is 'down' (as without these settings)


Shutting down interface eth0:  [  OK  ]
Shutting down interface eth1:  [  OK  ]
Shutting down interface eth2:  [  OK  ]
Shutting down loopback interface:  Could not load file '/etc/sysconfig/network-scripts/ifcfg-lo'
Could not load file '/etc/sysconfig/network-scripts/ifcfg-lo'
Could not load file '/etc/sysconfig/network-scripts/ifcfg-lo'
Could not load file '/etc/sysconfig/network-scripts/ifcfg-lo'
[  OK  ]
Bringing up loopback interface:  Could not load file '/etc/sysconfig/network-scripts/ifcfg-lo'
Could not load file '/etc/sysconfig/network-scripts/ifcfg-lo'
Could not load file '/etc/sysconfig/network-scripts/ifcfg-lo'
Could not load file '/etc/sysconfig/network-scripts/ifcfg-lo'
[  OK  ]
Bringing up interface eth0:  Connection successfully activated (D-Bus active path: /org/freedesktop/NetworkManager/ActiveConnection/3)
[  OK  ]
Bringing up interface eth1:  Error: Connection activation failed: Master connection not found or invalid
[FAILED]
Bringing up interface eth2:  Error: Connection activation failed: Master connection not found or invalid
[FAILED]
Bringing up interface team0:  [  OK  ]
Comment 4 Lukáš Nykrýn 2015-05-11 14:56:40 UTC 
Can you try this?


export SYSTEMCTL_SKIP_REDIRECT=1
service network stop
nmcli connection reload
service network start
Comment 5 Marek Grac 2015-05-11 15:04:29 UTC 
@Lukáš:

This one, works for me.
Comment 6 Lukáš Nykrýn 2015-05-11 15:17:37 UTC 
Upstream patch (with a cool hash):
https://git.fedorahosted.org/cgit/initscripts.git/commit/?id=474747
Comment 10 errata-xmlrpc 2015-11-19 11:23:51 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-2134.html
Note You need to log in before you can comment on or make changes to this bug.