Thank you all for your suggestions. I appreciate the discussion.

There are two network statements in the kick start file because that is
the way that Anaconda creates /root/anaconda-ks.cfg. You may recall that
anaconda-ks.cfg is the file of kick start statements created when a
configuration is specified with the GUI. When the Hostname is specified
at the bottom of the Network Configuration screen the second network 
statement is added to anaconda-ks.cfg:

network --hostname=lamp.hunter.org

I was following Anaconda's pattern. 

I tried again after combining the options of the two network statements
into a single statement. Now everything works as expected. I was certain 
that I had tried this once before without the expected results. I was 
obviously confused.

Thank you again.

On Mon, 2013-03-25 at 12:59 +0000, Kovacs, Corey J. wrote:
> For what it's worth, my experience has always been a second network line will 
> override settings on the first. As DHCP is the default, maybe that's got 
> something to do with it. 
> 
> It does appear that you are trying to configure things on two separate lines 
> for the same interface. That's not going to work as that's not the way those 
> "commands" are meant to be used (as far as I know anyway).
> 
> I think Michael is right in that you should probably combine it all into one 
> line.
> 
> A bigger question though, it seems, is why NetworkManager is ignoring the 
> config?
> 
> One thing to try is disabling NetworkManager, and or add the 
> "NM_CONTROLLED=no" line to the ifcfg-eth0 file as well.
> 
> Simply take NetworkManager out of the loop to eliminate it as a potential 
> problem area.
> 
> Good luck
> 
> -C
> 
> 
> Corey Kovacs
> Sr. System Architect
> Technology Management Associates
> RHCA: 110-541-489
> 
> ________________________________________
> From: [email protected] [[email protected]] 
> on behalf of Michael Mayer [[email protected]]
> Sent: Monday, March 25, 2013 3:01 AM
> To: [email protected]
> Subject: Re: Static IP Addressing
> 
> Dean, just wondering:
> 
> Does the problem persist if you combine the two "network" lines into
> one, i.e. use
> 
> network --activate --bootproto=static --device=eth0
> --gateway=192.168.1.254 --ip=192.168.1.12 --nameserver=75.75.76.76
> --netmask=255.255.255.0 --noipv6 --hostname=lamp.hunter.org
> 
> 
> Michael.
> 
> 
> On 03/24/2013 11:13 PM, Dean Hunter wrote:
> > No, there is only the one network. Something does not like my
> > specification of a static IP address and replaces it with a default DHCP
> > configuration. I have the same problem on every machine I try to specify
> > a static IP address.
> >
> > On Sun, 2013-03-24 at 10:54 -0400, Harry Hoffman wrote:
> >> Is there a spurious network in there?
> >>
> >> -------- Original Message --------
> >> From: Dean Hunter
> >> Sent: Sat, Mar 23, 2013 10:30 PM
> >> To: [email protected]
> >> CC:
> >> Subject: Static IP Addressing
> >>
> >>
> >>
> >> Why does this kickstart file:
> >>
> >> authconfig --enableshadow --passalgo=sha512
> >> autopart --type=lvm
> >> bootloader --boot-drive=vda --location=mbr
> >> cdrom
> >> clearpart --all --drives=vda --initlabel
> >> firstboot --disable
> >> ignoredisk --only-use=vda
> >> install
> >> keyboard --vckeymap=us --xlayouts=us
> >> lang en_US.UTF-8
> >> network --activate --bootproto=static --device=eth0
> >> --gateway=192.168.1.254 --ip=192.168.1.12 --nameserver=75.75.76.76
> >> --netmask=255.255.255.0 --noipv6
> >> network --hostname=lamp.hunter.org
> >> rootpw --iscrypted \$6\$82gtiKgE7AvH./ic\
> >> $TeDjrPrkQ19ULsPEzxStyqzkfRaGvKn0NpSB4ekV98hJOABaO5uQDzQmlCy8t7RwytXzS3t/yRyGZA.8ez2wf/
> >> reboot
> >> text
> >> timezone America/Chicago --isUtc --ntpservers=192.168.1.11
> >> xconfig --startxonboot
> >>
> >> produce this network configuration:
> >>
> >> 22:52:57,773 DEBUG ifcfg: content of files (network initialization):
> >> 22:52:57,774 DEBUG ifcfg: /etc/sysconfig/network-scripts/ifcfg-eth0:
> >> # Generated by dracut initrd
> >> DEVICE=eth0
> >> ONBOOT=yes
> >> NETBOOT=yes
> >> UUID=5edcb3fc-f4b5-4ce7-98d2-bde0f02a5e2b
> >> BOOTPROTO=none
> >> IPADDR=
> >> PREFIX=
> >> HWADDR="52:54:00:19:88:c9"
> >> TYPE=Ethernet
> >> NAME="Boot Disk"
> >> DNS1=75.75.76.76
> >>
> >> 22:52:57,819 DEBUG ifcfg:
> >> loadIfcfFile /etc/sysconfig/network-scripts/ifcfg-eth0
> >> 22:52:57,830 DEBUG ifcfg: NetworkDevice eth0 set: ONBOOT=yes
> >> 22:52:57,834 DEBUG ifcfg: writeIfcfgFile eth0
> >> to /etc/sysconfig/network-scripts/ifcfg-eth0 not needed
> >> 22:52:57,870 DEBUG ifcfg:
> >> loadIfcfFile /etc/sysconfig/network-scripts/ifcfg-eth0
> >> 22:52:57,872 DEBUG ifcfg: NetworkDevice eth0 set: ONBOOT=yes
> >> 22:52:57,873 DEBUG ifcfg: writeIfcfgFile eth0
> >> to /etc/sysconfig/network-scripts/ifcfg-eth0 not needed
> >> 23:02:32,739 DEBUG ifcfg:
> >> loadIfcfFile /etc/sysconfig/network-scripts/ifcfg-eth0
> >> 23:02:32,756 DEBUG ifcfg:
> >> loadIfcfFile /mnt/sysimage/etc/sysconfig/network-scripts/ifcfg-eth0
> >>
> >> _______________________________________________
> >> Kickstart-list mailing list
> >> [email protected]
> >> https://www.redhat.com/mailman/listinfo/kickstart-list
> >
> > _______________________________________________
> > Kickstart-list mailing list
> > [email protected]
> > https://www.redhat.com/mailman/listinfo/kickstart-list
> 
> _______________________________________________
> Kickstart-list mailing list
> [email protected]
> https://www.redhat.com/mailman/listinfo/kickstart-list
> 
> 





_______________________________________________
Kickstart-list mailing list
[email protected]
https://www.redhat.com/mailman/listinfo/kickstart-list

Reply via email to