Bug 117481 – Kickstart script has bootproto of dhcp rather than static

This service will be undergoing maintenance at 00:00 UTC, 2016-09-28. It is expected to last about 1 hours

Bug 117481 - Kickstart script has bootproto of dhcp rather than static

Summary:	Kickstart script has bootproto of dhcp rather than static

Status:	CLOSED DUPLICATE of bug 115481

Aliases:	None

Product:	Red Hat Satellite 5
Classification:	Red Hat
Component:	Server (Show other bugs)
Sub Component:
Version:	unspecified
Hardware:	All Linux

Priority	medium Severity medium
Target Milestone:	---
Target Release:	---
Assigned To:	Robin Norwood
QA Contact:	Fanny Augustin
Docs Contact:

URL:
Whiteboard:
Keywords:

Depends On:
Blocks:	113026
	Show dependency tree / graph

Reported:	2004-03-04 09:40 EST by Terry Jones
Modified:	2007-07-31 10:30 EDT (History)
CC List:	1 user (show)

See Also:
Fixed In Version:
Doc Type:	Bug Fix
Doc Text:
Story Points:	---
Clone Of:
Environment:
Last Closed:	2006-02-21 14:01:48 EST
Type:	---
Regression:	---
Mount Type:	---
Documentation:	---
CRM:
Verified Versions:
Category:	---
oVirt Team:	---
RHEL 7.3 requirements from Atomic Host:

Attachments	(Terms of Use)
Add an attachment (proposed patch, testcase, etc.)

Groups: None (edit)

Description Terry Jones 2004-03-04 09:40:28 EST

Description of problem:
Using provisioning.
Create a kickstart script and specify static ip addresses using eth0.
Script generated has --bootproto dhcp but should be --bootproto static

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

How reproducible:
Create a kickstart script

Steps to Reproduce:
1. Create Kickstart script
2. Set network to "use static ip from interface eth0"
3. Generate script
4. Examine details
  
Actual results:


Expected results:


Additional info:

Comment 1 Terry Jones 2004-03-04 10:10:23 EST

Duplicate of 115481 - please close

Comment 2 Robin Norwood 2004-03-04 10:20:03 EST

Yep, closing.

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

Comment 3 Red Hat Bugzilla 2006-02-21 14:01:48 EST

Changed to 'CLOSED' state since 'RESOLVED' has been deprecated.

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