- openSUSE Autoinstall

Re: [opensuse-autoinstall] autoyast and vlan
by 686f6c6d 19 Nov '10

19 Nov '10

On Fri, Nov 19, 2010 at 08:32, <Dirk.Lohmann(a)bertelsmann.de> wrote: > Hello, Hi. I'm unsure again if your mail was supposed to go only to me, but i'm replying to the list so everyone can benefit from our infinite wisdom. (; > we try to solved the Problem with this shell script in initrd and it is working. > But there is one blemishes. Yast is starting and then we have to klick through. > > #!/bin/bash > # > # Autor: buss18 > > # Convert CMDLINE options to variables > cat /proc/cmdline | /bin/sed 's/ /\n/g' > /tmp/networkinfo > > source /tmp/networkinfo > > # Load VLAN Module > /sbin/modprobe 8021q > > # Configure Interface > /sbin/vconfig add eth0 $vlan > /sbin/ifconfig eth0 up > /sbin/ifconfig eth0.$vlan $hostip netmask $netmask > /sbin/ifconfig eth0.$vlan up > /sbin/route add default gw $gateway > > # Sleep and ping gateway > sleep 5 > /sbin/arping -c 5 $gateway > /bin/ping -c 5 $gateway That sounds like progress! So... 1) Are you still using your autoyast= parameters as before? 2) Do you actually need the initrd (eg. because the module is not in the regular kernel)? Otherwise, I would just use the normal kernel and move your script from the initrd into <pre-scripts>. It should work without changes. tty, 686f6c6d -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] /add_on_products.xml - User does not want to trust key
by Ruediger Gunreben 18 Nov '10

18 Nov '10

Hi, I'm currently building a SLES11 SP1 Image and using this customized CD for a pxe boot. During boot and scanning the /add_on_products.xml file the installation complains about the repository. In the y2log these comments werde made: ---- snip Callback ImportGpgKey not registered, using default value: false (verifyFileSignatureWorkflow):417 User does not want to trust key 62A0C0D5C5.... ---- snip Where is the switch to trust the key? The installation procedure then using a profiles directory structure with the same repositories in. In this case everything works well - In the profiles xml file the gpg/pgp switch are all set to trust unknown keys. Thanks in advance Regards Ruediger -- Ruediger Gunreben -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 3

Fwd: [opensuse-autoinstall] autoyast and vlan
by 686f6c6d 16 Nov '10

16 Nov '10

Sorry again, I only bcc'ed this mail to the list, which apparently caused it to disappear. tty, 686f6c6d ---------- Forwarded message ---------- From: 686f6c6d <686f6c6d(a)googlemail.com> Date: Tue, Nov 16, 2010 at 13:32 Subject: Re: [opensuse-autoinstall] autoyast and vlan To: Dirk.Lohmann(a)bertelsmann.de On Mon, Nov 15, 2010 at 10:40, <Dirk.Lohmann(a)bertelsmann.de> wrote: > Hello, > we are using the SELS11 minicd with costum-made initrd. > If we boot with minicd, we boot into a graphical menu because we must configure the vlan there. Ok, first of all, please take your time to read my email from 2010-11-14 and answer the questions, one by one, if that is possible. Otherwise we're running in circles here. > After we configured the vlan manuely the installation is going on. But after the first reboot we have to configure the vlan again. Yes, I tried to answer that before, but I left out some important details it seems. (; The thing is, if you configure your network manually, (to my knowledge) autoyast has no way of knowing that, and hence you have to configure it manually *again* in stage 2 in this case. It is certainly debatable if this autoyast behaviour makes sense. I myself would like it very much if autoyast would, for example, extend <keep_install_network> to also remember a manually set-up network. (Uwe: Are there reasons why this wouldn't work or is a stupid idea?) However, the best option I found in your case was the one I was referring to in my long mail from before: - Put the commands you did manually in a shell script (because they look like they can be automated to a very high degree) - Put a small autoyast profile (autoinst.xml in my setup) on the boot CD with scripts to: - bring up the network as you would do manually (you can also use ask-scripts to fetch user input) - fetch the second profile (net.xml in my setup) from a webserver (if you use one) and fetch it to, like, /tmp/stage2.xml - patch your already-manually-set network settings into that new autoyast profile and then move the file to /tmp/profile/modified.xml (This way, autoyast will use your user-input network settings in stage 2!) As a - lesser - alternative to the last point, you could instead use a script that "rescues" your file to stage2 and bring the network up by script from these values again. But then you still have to set it up manually *again* because you never told autoyast the machine should have a network configuration. How the exact VLAN section of the autoyast profile must look like you can best find out if you clone an existing server's settings. HTH, 686f6c6d -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

Re: [opensuse-autoinstall] autoyast and vlan
by 686f6c6d 16 Nov '10

16 Nov '10

On Tue, Nov 16, 2010 at 13:32, 686f6c6d <686f6c6d(a)googlemail.com> wrote: > As a - lesser - alternative to the last point, you could instead use a > script that "rescues" your file to stage2 and bring the network up by > script from these values again. Sorry, what I mean by "your file" is the files where you saved your ask-script values to. tty, 686f6c6d -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] autoyast and vlan
by Dirk.Lohmann＠Bertelsmann.de 13 Nov '10

13 Nov '10

Hello Is there a resolution for installing vlan now ? We start the autoyast installation with bootcd and have to configure the vlan afterwards. But we want this to do automaticly. We try it to build a spezial initrd. Vlan is configured then but it is not working. The next Problem is, that we have to configure the vlan config after the first reboot again We configure vlan like this VLAN Konfiguration bei installation. Erst mal ganz normale installation über autoyast Wenn SUSE nach dem Installationserver fragt ALT F9 betätigen um eine Console zu bekommen. Dann den vlan treiber laden mit: modprobe 8021q wenn z.b. 3963 das Dialog vlan ist mit ifconfig eth0 auf irgendeine private ip legen. vconfig add eth0 3963 Das darduch erzeugte device muss jetzt mit der eigentlich Dialog IP konfiguriert werden. Die Route nicht vergessen. Danach mit F1 zurück in den Installationmodus wechseln und ganz normal installieren. Nach dem ersten boot möchte SUSE noch den Postinstall durchführen der auf die Nase fällt, dort muss leider das ganze noch mal gemacht werden. Nach Installation konfigurieren wir das Netz richtig über yast. (a)dd Device Type Bond ed(i)t Bond B(o)nd Slaves ( Die beiden eth Devices für das Bonding auswählen ) (a)dd Device Type VLAN con(f)iguration Name <VlanNummer> (N)ext Real Interface for (V)LAN bond0 und die IP konfigureren. Fertig Dirk Lohmann -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

2 1

Re: [opensuse-autoinstall] how to configure services using autoyast
by 686f6c6d 12 Nov '10

12 Nov '10

On Thu, Nov 11, 2010 at 20:23, Yiping Zhang <yiping4698(a)gmail.com> wrote: > On Thu, Nov 11, 2010 at 2:03 AM, 686f6c6d <686f6c6d(a)googlemail.com> wrote: >> On Sat, Nov 6, 2010 at 00:22, Yiping Zhang <yiping4698(a)gmail.com> wrote: >>> HI, >>> >>> In my autoyast.xml, I want to enable a number of services like >>> autofs, snmpd, ntp etc. I have put them in <runlevel> section as >>> below: >> >> As long as the package "yast2-runlevel" is installed, the following >> works for me. > > > That's it, I thought I had included yast2-runlevel package in my > installation, but apparently not! Once I added yast2-runlevel to the > package list, services are enabled properly after installation! > > I just wish that autoyast could provide some error message for missing > dependents, rather than just ignore it. > > Thanks Great to see it helped. I often run into this type of problems because we make heavy use of <remove-packages>. \: tty, 686f6c6d -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] SLES11 best way to eject media at end of stage1?
by Stepan, Troy 11 Nov '10

11 Nov '10

Hi all, In SLES10 I used a <chroot-script> to eject the CD at the end of stage 1 before the reboot. In SLES11 this doesn't work because YaST installs the sles-release RPM in stage 2 after the reboot. As a workaround I moved the script to an <init-script> but wanted to know if there was a better way to do this. i.e. - can I make sles-release install in stage 1 with the rest of the other RPMs? -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

Re: [opensuse-autoinstall] how to configure services using autoyast
by Oliver Schweikert 11 Nov '10

11 Nov '10

Yiping Zhang schrieb: > Thanks, but it did not help. > > I looked at schema file > /usr/share/YaST2/schema/autoyast/rng/runlevels.rng, "enabled" tag is > not defined under "service" entry. Only following elements are > defined: > > service_name > service_start > service_stop > service_status > > I also tried adding <service_status>enable</service_status> to all > these services, still no luck. > > Any other ideas ? I was mistaken, it must be <service_status>enable</service_status> The ,,enabled''-tag is for inetd services, sorry! :-( Regards, Oliver -- Oliver Schweikert Software Development HORIBA Europe Automation Division GmbH Zabergäustr. 3 73765 Neuhausen (Germany) Tel: +49 7158-933-413 Fax: +49 7158-933-613 Email: oliver.schweikert(a)horiba.com Geschäftsführer: Thomas E. Ehmann, Yuichi Muroga, Takashi Nagano Amtsgericht Stuttgart, HRB 213200 -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

1 0

[opensuse-autoinstall] how to configure services using autoyast
by Yiping Zhang 11 Nov '10

11 Nov '10

HI, In my autoyast.xml, I want to enable a number of services like autofs, snmpd, ntp etc. I have put them in <runlevel> section as below: <runlevel xmlns=""> <default>3</default> <services config:type="list"> <service> <service_name>autofs</service_name> <service_start>3 5</service_start> </service> <service> <service_name>ntp</service_name> <service_start>3 5</service_start> </service> <service> <service_name>snmpd</service_name> <service_start>3 5</service_start> </service> ..... </runlevel> But after server is installed, chckconfig indicates all these services are left at off state for all run levels. What did I miss ? Thanks -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 2

[opensuse-autoinstall] Adding packages to profile triggers error message
by Isaac Hailperin 07 Nov '10

07 Nov '10

Hi, I try to install sles 11 via autoyast. I did an installation from dvd, and pulled an autoyast profile. This profile works, and can be installed via pxe. Now I want to add the following packages: findutils-locate, dhcp-server, bind, apache2, vsftpd, nfs-kernel-server I do this via the gui. I have also tried to do it with an editor, as the gui messed up profiles in sles10sp2. In both cases, after the first reboot, I get the errormessage: "The package resolver run failed. Please check your software section in the aut" [oyast profile] (last part invisible, I guess it should be the software section in my autoyast profile :-)) This a real problem, as I have to confirm this message, thus it stops the autoinstall process. After confirming, the autoinstall process continues. Right bevor I can log in, I get "Could not update ICEauthority file /var/lib/gdm/.ICEauthority" I confirm, and get: "There is a problem with the configuration server. (/usr/lib/GConf/2/gconf-sanity-check-2 exited with status 256)" I confirm, and can log in. Theses messages are presistend after reboot. Its annoying, but not a stopper like the first problem. Why is this? Can I avoid this? Isaac -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

3 2