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.

Bug 1102101

Summary: Can't do %include in kickstart to configure network
Product: Red Hat Enterprise Linux 7 Reporter: Trond H. Amundsen <trondham>
Component: anacondaAssignee: Radek Vykydal <rvykydal>
Status: CLOSED DUPLICATE QA Contact: Release Test Team <release-test-team-automation>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 7.0CC: rvykydal
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2014-05-28 13:53:10 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
anaconda.log
none
ifcfg.log
none
syslog
none
The /tmp/net-include file (containing kickstart network command) none

Description Trond H. Amundsen 2014-05-28 13:30:31 UTC
Description of problem:

In our environment, we use DHCP during install, but want the host to have a static network configuration. To achieve this, we do some logic in %pre:

1. prompt the user for the hostname
2. look up IP, netmask etc. using a local cgi script
3. create the network line as /tmp/net-include

In kickstart, we do "%include /tmp/net-include" to configure the network. This doesn't work, however. If I take the specific network command in "/tmp/net-include" and use that directly in kickstart (instead of %include) it works.

So, it seems I can't do %include to configure the network. This used to work in rhel6 anaconda, but not rhel7 and recent fedoras.

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

How reproducible:
Always

Steps to Reproduce:
1. Create /tmp/net-include with static IP in %pre
2. Do "%include /tmp/net-include" in kickstart

Actual results:
No static network as configured.

Expected results:
Static network as configured

Additional info:
I'll attach relevant log files and the /tmp/net-include file.

Comment 1 Trond H. Amundsen 2014-05-28 13:31:20 UTC
Created attachment 899980 [details]
anaconda.log

Comment 2 Trond H. Amundsen 2014-05-28 13:31:56 UTC
Created attachment 899981 [details]
ifcfg.log

Comment 3 Trond H. Amundsen 2014-05-28 13:32:26 UTC
Created attachment 899982 [details]
syslog

Comment 4 Trond H. Amundsen 2014-05-28 13:33:05 UTC
Created attachment 899983 [details]
The /tmp/net-include file (containing kickstart network command)

Comment 5 Radek Vykydal 2014-05-28 13:53:10 UTC
This is caused by a bug in NetworkManager connection matching that has been fixed in Release Candidate 3.

*** This bug has been marked as a duplicate of bug 1083153 ***