From rhayden.public at gmail.com Wed Mar 6 22:54:34 2013 From: rhayden.public at gmail.com (Robert Hayden) Date: Wed, 6 Mar 2013 16:54:34 -0600 Subject: Members may not be specified for preexisting volgroup Message-ID: This is my first post on this particular listserv, so please bare with me. I have also read through the last few years of posts without finding answers to my question. So, I thought I would ask the community before logging a support ticket with Red Hat. I am trying to isolate a kickstart issue with RHEL 6.4 using anaconda 13.21.195. Hardware is HP ProLiant BL460c G7. I have SAN storage and an internal hard drive. In the %pre script, I am removing the lpfc kernel module and loading the hpsa module. Only the internal drive is available when I review the anaconda session in tty2. Issue: My kickstart session is aborting with the following message: -------------start cut------------------ The following error was found while parsing the kickstart configuration file: The following problem occurred on line 38 of the kickstart file: Members may not be specified for preexisting volgroup install exited abnormally [1/1] The system will be rebooted when you press Ctrl-C or Ctrl-Alt-Delete. ----------------end cut--------------- My partition section in the kickstart is as follows with line 38 being the volgroup line: --------------start cut-------------------- bootloader --location=mbr --driveorder=sda --append="crashkernel=auto rhgb quiet" clearpart --none part /boot --fstype=ext4 --onpart=sda1 part pv.008002 --onpart=sda2 --noformat volgroup vg00 --pesize=32768 --useexisting --noformat pv.008002 logvol / --fstype=ext4 --name=rootlv00 --vgname=vg00 --useexisting logvol /tmp --fstype=ext4 --name=tmplv00 --vgname=vg00 --useexisting logvol /home --fstype=ext3 --name=homelv00 --vgname=vg00 --useexisting --noformat logvol /u02 --fstype=ext3 --name=diaglv00 --vgname=vg00 --useexisting --noformat logvol /opt --fstype=ext3 --name=optlv00 --vgname=vg00 --useexisting --noformat logvol /opt/stage --fstype=ext3 --name=optstagelv00 --vgname=vg00 --useexisting --noformat logvol /usr --fstype=ext4 --name=usrlv00 --vgname=vg00 --useexisting logvol /u01 --fstype=ext3 --name=u01lv00 --vgname=vg00 --useexisting --noformat logvol /usr/local --fstype=ext3 --name=usrlocallv00 --vgname=vg00 --useexisting --noformat logvol /var --fstype=ext4 --name=varlv00 --vgname=vg00 --useexisting logvol swap --name=swaplv00 --vgname=vg00 --useexisting -------------------------end cut---------------------- What I am attempting to do is install over a RHEL 5 machine, reusing/formating core file systems like /etc and /var while keeping user data file systems like /u01 and /opt intact. The idea is to do a variation of a fresh install instead of an in-place upgrade. The "upgradeany" option from RHEL 5 to RHEL 6 leaves too much junk compared to the 4 to 5 jump. The GUI version of anaconda will allow me to pick and choose which file systems to reformat and which to skip. That works fine for my use case. The attempt on the partitioning section above was using the anaconda-ks.cfg from the interactive installation as a starting point. I have completed a wide variation of combinations with the parameters --noformat and --useexisting and have not hit the correct combination yet. I have also scanned the source code for anaconda and cannot find the phrase "Members may not", so I am not even sure where the code is aborting. When I switch to tty2 for troubleshooting, the last file touched in /tmp is the storage.log with multipath being used to scan devices. I see /dev/sda*, but /dev/mapper directory only contains "control" special file. Unsure if that is makes a difference, since I am using the --onpart=sda2 for the volume group. I am looking for suggestions on how to format the kickstart file to be able to skip file systems on a fresh installation. Or, some direction in how to step through or debug anaconda to determine where in the process it aborts. This is an R&D machine, so I can pretty much toast it on a whim. Sincerely Robert From rhayden.public at gmail.com Thu Mar 7 22:26:19 2013 From: rhayden.public at gmail.com (Robert Hayden) Date: Thu, 7 Mar 2013 16:26:19 -0600 Subject: Members may not be specified for preexisting volgroup In-Reply-To: References: Message-ID: Found the issue, but not a solution on this. Logged a support ticket with Red Hat. Code was in pykickstart RPM, in particular pykickstart/commands/volgroup.py. Appears to be introduced with version 1.74.12-1 or 1.74.11-1. I was able to isolate the python code by doing the following: 1) Download and unzip pykickstart source into /tmp on another RHEL 6.4 machine. 2) Place the ks.cfg file, stolen from the failed kickstart attempt (use scp to copy it from tty2 sessin), into the top level directory. 3) Use the following python code, modified from [1], to read the ks.cfg, parse it, and attempt to write out the parsed contents. --------------start cut----------- #!/usr/bin/python from pykickstart.parser import * from pykickstart.version import makeVersion ksparser = KickstartParser(makeVersion()) ksparser.readKickstart("/tmp/pykickstart-1.74.12/ks.cfg") outfile = open("out.cfg", "w") outfile.write(ksparser.handler.__str__()) outfile.close() -------------end cut-------------- The output of the python script dumps the same error that I see in the anaconda window on a failed kickstart. This allowed me to troubleshoot and modify the volgroup.py to print out variables without having to do a full blown kickstart. Hope that helps someone down the road. I will report back the final solution when I am done with Red Hat. Thanks Robert [1] https://fedoraproject.org/wiki/PykickstartIntro From rhayden.public at gmail.com Mon Mar 11 21:41:21 2013 From: rhayden.public at gmail.com (Robert Hayden) Date: Mon, 11 Mar 2013 16:41:21 -0500 Subject: Members may not be specified for preexisting volgroup In-Reply-To: References: Message-ID: Final update. Ends up that the "pv.008002" element on the "volgroup" line in the kickstart was causing the error. If I removed that and let kickstart find the proper logical volumes associated to the volume group on its own, then kickstart continued. So, there is a disconnect between the anaconda-ks.cfg file generated if you install manually (skipping file systems) and the creation of a pure kickstart installation stanzas. I am unsure if Red Hat will pursue the issue any further now that there is a solution. Thanks Robert From DeanHunter at comcast.net Sat Mar 23 17:30:27 2013 From: DeanHunter at comcast.net (Dean Hunter) Date: Sat, 23 Mar 2013 12:30:27 -0500 Subject: Network Configuration Message-ID: <1364059827.2992.3.camel@host.hunter.org> Is there an option for the network configuration that will set "DOMAIN=" in the ifcfg-* files? From hhoffman at ip-solutions.net Sat Mar 23 18:59:13 2013 From: hhoffman at ip-solutions.net (Harry Hoffman) Date: Sat, 23 Mar 2013 14:59:13 -0400 Subject: Network Configuration In-Reply-To: <1364059827.2992.3.camel@host.hunter.org> References: <1364059827.2992.3.camel@host.hunter.org> Message-ID: <514DFB81.9010203@ip-solutions.net> network --nameserver= I think this only works for static ip addresses. Cheers, Harry On 03/23/2013 01:30 PM, Dean Hunter wrote: > Is there an option for the network configuration that will set "DOMAIN=" > in the ifcfg-* files? > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > From DeanHunter at comcast.net Sun Mar 24 02:30:44 2013 From: DeanHunter at comcast.net (Dean Hunter) Date: Sat, 23 Mar 2013 21:30:44 -0500 Subject: Static IP Addressing Message-ID: <1364092244.2992.6.camel@host.hunter.org> 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 From hhoffman at ip-solutions.net Sun Mar 24 14:54:29 2013 From: hhoffman at ip-solutions.net (Harry Hoffman) Date: Sun, 24 Mar 2013 10:54:29 -0400 Subject: Static IP Addressing Message-ID: An HTML attachment was scrubbed... URL: From DeanHunter at comcast.net Sun Mar 24 22:13:45 2013 From: DeanHunter at comcast.net (Dean Hunter) Date: Sun, 24 Mar 2013 17:13:45 -0500 Subject: Static IP Addressing In-Reply-To: References: Message-ID: <1364163225.2493.3.camel@host.hunter.org> 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: kickstart-list at redhat.com > 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 > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From DeanHunter at comcast.net Sun Mar 24 22:20:29 2013 From: DeanHunter at comcast.net (Dean Hunter) Date: Sun, 24 Mar 2013 17:20:29 -0500 Subject: Network Configuration In-Reply-To: <514DFB81.9010203@ip-solutions.net> References: <1364059827.2992.3.camel@host.hunter.org> <514DFB81.9010203@ip-solutions.net> Message-ID: <1364163629.2493.8.camel@host.hunter.org> The kick start network option "--nameserver=" is the equivalent of the ifcfg-* script statement "DNS1=". I am looking for the kick start equivalent of the ipcfg-* script statement "DOMAIN=". This defines the default DNS search domain for host names that are not fully qualified. On Sat, 2013-03-23 at 14:59 -0400, Harry Hoffman wrote: > network --nameserver= > I think this only works for static ip addresses. > > Cheers, > Harry > > On 03/23/2013 01:30 PM, Dean Hunter wrote: > > Is there an option for the network configuration that will set "DOMAIN=" > > in the ifcfg-* files? > > > > _______________________________________________ > > Kickstart-list mailing list > > Kickstart-list at redhat.com > > https://www.redhat.com/mailman/listinfo/kickstart-list > > > > From hhoffman at ip-solutions.net Sun Mar 24 23:45:14 2013 From: hhoffman at ip-solutions.net (Harry Hoffman) Date: Sun, 24 Mar 2013 19:45:14 -0400 Subject: Static IP Addressing Message-ID: <3wiryb03d3yypuu73rwc909q.1364168714729@email.android.com> An HTML attachment was scrubbed... URL: From michael at mayer.cx Mon Mar 25 07:01:35 2013 From: michael at mayer.cx (Michael Mayer) Date: Mon, 25 Mar 2013 08:01:35 +0100 Subject: Static IP Addressing In-Reply-To: <1364163225.2493.3.camel@host.hunter.org> References: <1364163225.2493.3.camel@host.hunter.org> Message-ID: <514FF64F.7070207@mayer.cx> 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: kickstart-list at redhat.com >> 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 >> Kickstart-list at redhat.com >> https://www.redhat.com/mailman/listinfo/kickstart-list > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list From cjk at techma.com Mon Mar 25 12:59:17 2013 From: cjk at techma.com (Kovacs, Corey J.) Date: Mon, 25 Mar 2013 12:59:17 +0000 Subject: Static IP Addressing In-Reply-To: <514FF64F.7070207@mayer.cx> References: <1364163225.2493.3.camel@host.hunter.org>,<514FF64F.7070207@mayer.cx> Message-ID: 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: kickstart-list-bounces at redhat.com [kickstart-list-bounces at redhat.com] on behalf of Michael Mayer [michael at mayer.cx] Sent: Monday, March 25, 2013 3:01 AM To: kickstart-list at redhat.com 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: kickstart-list at redhat.com >> 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 >> Kickstart-list at redhat.com >> https://www.redhat.com/mailman/listinfo/kickstart-list > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list _______________________________________________ Kickstart-list mailing list Kickstart-list at redhat.com https://www.redhat.com/mailman/listinfo/kickstart-list From DeanHunter at comcast.net Tue Mar 26 01:20:02 2013 From: DeanHunter at comcast.net (Dean Hunter) Date: Mon, 25 Mar 2013 20:20:02 -0500 Subject: Static IP Addressing In-Reply-To: References: <1364163225.2493.3.camel@host.hunter.org>,<514FF64F.7070207@mayer.cx> Message-ID: <1364260802.2493.37.camel@host.hunter.org> 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: kickstart-list-bounces at redhat.com [kickstart-list-bounces at redhat.com] on behalf of Michael Mayer [michael at mayer.cx] > Sent: Monday, March 25, 2013 3:01 AM > To: kickstart-list at redhat.com > 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: kickstart-list at redhat.com > >> 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 > >> Kickstart-list at redhat.com > >> https://www.redhat.com/mailman/listinfo/kickstart-list > > > > _______________________________________________ > > Kickstart-list mailing list > > Kickstart-list at redhat.com > > https://www.redhat.com/mailman/listinfo/kickstart-list > > _______________________________________________ > Kickstart-list mailing list > Kickstart-list at redhat.com > https://www.redhat.com/mailman/listinfo/kickstart-list > > From bernd.nies at gmail.com Tue Mar 26 07:41:10 2013 From: bernd.nies at gmail.com (Bernd Nies) Date: Tue, 26 Mar 2013 08:41:10 +0100 Subject: Kickstart Partitioning: Define partition order Message-ID: Hi, We use the snipplet shown to create partitioning using kickstart on hundreds of development workstations and for development VMware virtual machines. # Disk Partitioning # Dynamically because it depends on disk device names %include /tmp/partitions.ks %pre PATH="/bin:/sbin:/usr/bin:/usr/sbin" set $(list-harddrives) let numd=$#/2 disk0=$1 cat >/tmp/partitions.ks <<==EOF== zerombr ignoredisk --only-use=${disk0} bootloader --location=mbr clearpart --all --drives=${disk0} --initlabel partition /boot/efi --ondisk=${disk0} --asprimary --fstype=vfat --label EFI --size=200 partition /boot --ondisk=${disk0} --asprimary --fstype=ext4 --label BOOT --size=500 partition swap --ondisk=${disk0} --asprimary --fstype=swap --label SWAP --recommended partition / --ondisk=${disk0} --asprimary --fstype=ext4 --label ROOT --size=4096 --grow ==EOF== %end After kickstarting the order of the created partitions differs from the order given in the kickstart file. It is: 1. /dev/sda1 /boot/efi 2. /dev/sda2 /boot 3. /dev/sda3 / 4. /dev/sda4 swap On workstations this is no problem having swap at the end of the disk. But in the VMware virtual machines it causes problems when one has to resize the root partition. An option would be LVM and just add another virtual disk but we would like to use traditional ext4 partitioning because LVM is not supported by gparted and resizing with gparted is easier. Another option would be to create a VM template and use swap as a separate vmdk disk file. My question is: How can I give the order I want the partitions in kickstart? The option --onpart works only if there is already a partitioning layout. Regards, Bernd -------------- next part -------------- An HTML attachment was scrubbed... URL: From DeanHunter at comcast.net Tue Mar 26 09:22:39 2013 From: DeanHunter at comcast.net (Dean Hunter) Date: Tue, 26 Mar 2013 04:22:39 -0500 Subject: Failed to get D-Bus connection Message-ID: <1364289759.9848.2.camel@host.hunter.org> Why do some configuration commands fail like this when used in the kickstart post script? # Configure the host names hostnamectl set-hostname test.hunter.org --static Failed to get D-Bus connection: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory hostnamectl set-hostname "VM Test" --pretty Failed to get D-Bus connection: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory hostnamectl Failed to get D-Bus connection: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory