Bug 1472475 - Using teamd during kickstart install causes hang
Using teamd during kickstart install causes hang
Status: NEW
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: anaconda (Show other bugs)
7.3
x86_64 Unspecified
unspecified Severity unspecified
: rc
: ---
Assigned To: Anaconda Maintenance Team
Release Test Team
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2017-07-18 16:40 EDT by Mike
Modified: 2017-07-18 16:40 EDT (History)
0 users

See Also:
Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed:
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)

  None (edit)
Description Mike 2017-07-18 16:40:30 EDT
Description of problem:
When using teamd with kickstart on the 1611 isos the network interface never comes up and loops continuously until it consumes all the available RAM.

Version-Release number of selected component (if applicable):
7.3.1611

How reproducible:
Happens every time when tested on 7.3.1611 DVD or Minimal isos (untested on others)

Steps to Reproduce:
1. Boot into CentOS 7.3.1611 install CD
2. Add kickstart flags like so:
ks=http://example.com/path/file.txt ip=10.0.0.100::10.0.0.1:255.255.255.0:servername.example.com:team0:none team=team0:eth0,eth1 nameserver=10.0.0.10 net.ifnames=0

Actual results:
Installer attempts to configure the network interfaces, but hangs until it runs out of RAM with messages like:
ifup: fork: Cannot allocate memory

Expected results:
Installer configures the network interface and continues with installation

Additional info:
Using the same configuration line on the 7.2.1511 iso images works fine

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