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 1039532

Summary: What are the alternatives of `network --bootproto=query` in Red Hat Enterprise Linux 6.5?
Product: Red Hat Enterprise Linux 6 Reporter: Txxk <13427691965>
Component: pykickstartAssignee: Anaconda Maintenance Team <anaconda-maint-list>
Status: CLOSED NOTABUG QA Contact: Release Test Team <release-test-team-automation>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.5CC: dshea
Target Milestone: rc   
Target Release: ---   
Hardware: All   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-09 15:38:24 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:

Description Txxk 2013-12-09 11:06:45 UTC
Description of problem:


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

How reproducible:
My ks.cfg refer to this link https://access.redhat.com/site/documentation/zh-CN/Red_Hat_Enterprise_Linux/6/html/Migration_Planning_Guide/ch02s02s02.html  the said if do not set "network" the will hint you set network information to the NIC, but Centos6.5 did not do that.

Steps to Reproduce:
1.
2.
3.

Actual results:
In the Centos 5.5 ISO with kickstart,I set "network bootproto=query "to the configuration file,when i install system, hint me set network information to the NIC. But Centos6.5 did not do that.When system install success, I see the eth0 configuration file "bootproto=query" 

Expected results:
Install Centos6.5 with kickstart 

Additional info:
https://access.redhat.com/site/documentation/zh-CN/Red_Hat_Enterprise_Linux/6/html/Migration_Planning_Guide/ch02s02s02.html

Comment 1 Txxk 2013-12-09 11:54:58 UTC
i fix it, add "asknetwork" option the isolinux.cfg like append ks=cdrom:/isolinux/ks.cfg asknetwork initrd=initrd.img

Comment 2 David Shea 2013-12-09 15:38:24 UTC
While Red Hat welcomes bug reports on Red Hat products here in our public bugzilla database, please keep in mind that bugzilla is not a support tool or means of accessing support.  If you would like technical support please visit our support portal at access.redhat.com or call us for information on subscription offerings to suit your needs.