Bug 1254929 - network team device configuration in kickstart pre section not working
network team device configuration in kickstart pre section not working
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda (Show other bugs)
Unspecified Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Radek Vykydal
Release Test Team
Depends On: 1366300
  Show dependency treegraph
Reported: 2015-08-19 05:15 EDT by Radek Vykydal
Modified: 2016-11-03 19:09 EDT (History)
9 users (show)

See Also:
Fixed In Version: anaconda-
Doc Type: No Doc Update
Doc Text:
Story Points: ---
Clone Of:
: 1366300 (view as bug list)
Last Closed: 2016-11-03 19:09:12 EDT
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
A patch with two fixes (1.45 KB, patch)
2015-08-19 05:15 EDT, Radek Vykydal
no flags Details | Diff

  None (edit)
Description Radek Vykydal 2015-08-19 05:15:30 EDT
Created attachment 1064699 [details]
A patch with two fixes



Team device configuration in pre phase of kickstart does not work.

To reproduce:
- Have vm with 3 devices (eg ens3, ens7, ens8).
- Boot with ip=ens3:dhcp boot option (so that only ens3 is activated in dracut)
- Use one of these kickstarts

%include /tmp/ksinclude
echo 'network --device team0 --bootproto static --ip= --netmask= --gateway= --nameserver= --teamslaves=ens7,ens8 --teamconfig="{\"runner\": {\"name\": \"roundrobin\"}}" --activate' >> /tmp/ksinclude

%include /tmp/ksinclude
echo "network --device team0 --bootproto static --ip= --netmask= --gateway= --nameserver= --teamslaves=\"ens7'{\\\"prio\\\": -10, \\\"sticky\\\": true}',ens8'{\\\"prio\\\": 100}'\" --teamconfig=\"{\\\"runner\\\": {\\\"name\\\": \\\"activebackup\\\"}}\" --activate" >> /tmp/ksinclude

There are actually 2 fixes needed.

1) First one to make anaconda not crash on both (A) and (B).

2) Second one to actually use slave port configuration in (B), ie to have
TEAM_PORT_CONFIG="{\"prio\": 100}"
in /etc/sysconfig/network-scripts/ifcfg-ens8
based on ens8'{\\\"prio\\\": 100}' item of kickstart config
Comment 2 Radek Vykydal 2015-08-19 05:39:16 EDT
The patch is isolated and safe so I'm inclined to get this fix in rhel 7.2. OTOH I am not sure if defining team networking in pre kickstart is a widely used case.
Comment 4 Martin Banas 2015-09-08 09:27:37 EDT
Reproduced on RHEL-7.2-20150904.0, qa_ack+.
Comment 5 Radek Vykydal 2015-09-08 10:27:33 EDT
(In reply to Martin Banas from comment #4)
> Reproduced on RHEL-7.2-20150904.0, qa_ack+.

updates image for the compose:

Comment 6 LENHOF 2016-01-29 10:43:06 EST

This problem seem to affect me on my installation of RHEL 7.1, using network config in main kickstart file (without using pre).

Will probably move the config in a post-installation task...


Comment 8 Michal Kovarik 2016-07-27 08:57:13 EDT
Tested with anaconda-
Scenario (A) failed with:
anaconda for Red Hat Enterprise Linux 7.3 (pre-release) started.
 * installation log files are stored in /tmp during the installation
 * shell is available on TTY2
 * when reporting a bug add logs from /tmp as separate text/plain attachments
12:54:48 Running pre-installation scripts
Traceback (most recent call last):
  File "/sbin/anaconda", line 1202, in <module>
  File "/usr/lib64/python2.7/site-packages/pyanaconda/network.py", line 1298, in networkInitialize
  File "/usr/lib64/python2.7/site-packages/pyanaconda/network.py", line 1280, in apply_kickstart
    added_connections = add_connection_for_ksdata(network_data, dev_name)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/network.py", line 495, in add_connection_for_ksdata
    suuid = _add_slave_connection('team', slave, devname, networkdata.activate, svalues)
  File "/usr/lib64/python2.7/site-packages/pyanaconda/network.py", line 662, in _add_slave_connection
  File "/usr/lib64/python2.7/site-packages/pyanaconda/nm.py", line 908, in nm_add_connection
    connection = proxy.AddConnection('(a{sa{sv}})', settings)
  File "/usr/lib64/python2.7/site-packages/gi/overrides/Gio.py", line 171, in __call__
GLib.Error: g-io-error-quark: GDBus.Error:org.freedesktop.NetworkManager.Settings.Connection.InvalidProperty: team-port.config: value is NULL or empty (36)
Exception AttributeError: "'NoneType' object has no attribute 'udev_unref'" in <bound method Context.__del__ of <pyudev.core.Context object at 0x7fc529eb2290>> ignored

[anaconda root@localhost ~]# cat /tmp/ksinclude 
network --device team0 --bootproto static --ip= --netmask= --gateway= --nameserver= --teamslaves=eth1,eth2 --teamconfig="{\"runner\": {\"name\": \"roundrobin\"}}" --activate

Scenario (B) passed without issues.
Comment 9 Radek Vykydal 2016-07-29 05:46:24 EDT
Seems that NetworkManager started to require non-empty team port configration when creating team slave configuration (compared to 7.2 where empty port configuration would be accepted).

We can fix it by this patch:


I'd just like to confirm from NM whether the change is really intentional?
Comment 10 Radek Vykydal 2016-07-29 05:50:22 EDT
Updates image with the patch for anaconda-

Updates image with the patch for the latest anaconda-
Comment 11 Lubomir Rintel 2016-08-01 11:41:01 EDT
I think we want to preserve the ability to specify empty configuration.
Comment 12 Radek Vykydal 2016-08-24 07:42:35 EDT
So this should be fixed by NM bug 1366300.
Comment 14 Radek Vykydal 2016-08-25 06:55:44 EDT
(In reply to Radek Vykydal from comment #12)
> So this should be fixed by NM bug 1366300.

I've tested that it (adding "" port configuration) works with


which is unfortunately hitting another unrelated issue: bug 1370099.
Comment 17 Michal Kovarik 2016-09-09 04:31:07 EDT
Verified on RHEL-7.3-20160908.3 with anaconda- Both variants from description can be installed, configuration is also applied in installed system.
Comment 19 errata-xmlrpc 2016-11-03 19:09:12 EDT
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.


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