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:
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

After evaluating this issue, there are no plans to address it further or fix it in an upcoming release.  Therefore, it is being closed.  If plans change such that this issue will be fixed in an upcoming release, then the bug can be reopened.