openSUSE Autoinstall May 2011

autoinstall@lists.opensuse.org

13 participants
13 discussions

by John Willis

Does anyone know if any of the SLES releases 9 or 10 support passing the linuxrc option netdevice=<hardware mac address> ? I noticed Red Hat has had this for sometime and it seems totally missing in SuSE which seems really odd. I'm still scratching my head if we really are still passing only by kernel interface name. I read in the change log for linuxrc-1.8.6-3 a change that "sounds" like this feature. * Mon Mar 14 2005 - snwint(a)suse.de - s390: fix segfault in net_list_s390_devs() - extra root image was sometimes not used - allow netdevices to be specified by hwaddress But it looks like linuxrc-1.8.6-3 is only available in SuSE Professional 9.3. "any" commentary would be sincerely appreciated the feature also seems to be fairly minor since any delimiter seperating the octets in the hwaddr string could be used to identify the difference between an interface name and interface hw address if i could figure out a generic method of overriding the linuxrc with a custom script and daisy chain it back into linuxrc after setting up the interface name, I would.. and have a slight idea on how to do that.. but i'd rather find out i'm just missing something and the feature is already there Thanks!

8 years, 10 months

[opensuse-autoinstall] autoyast with multiple LVM Volume Groups

by big beer

Hello, I'm trying to have autoyast setup some LVM volume groups. I can get things setup with a single volume group, but if try to add 2 volume groups I seem to be running into some issue. I'm using the following xml inside the partitioning section to setup the PVs and add to the volume groups. . . . <drive> <device>/dev/sdb</device> <partitions config:type="list"> <partition> <lvm_group>firstvg</lvm_group> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> <drive> <device>/dev/sdc</device> <partitions config:type="list"> <partition> <lvm_group>secondvg</lvm_group> <partition_type>primary</partition_type> <size>max</size> </partition> </partitions> <use>all</use> </drive> . . . The problem is that both disks are configured as PVs in the same VG. Both sdb and sdc will be added to firstvg and secondvg will not exist. Am I trying this wrong or am I hitting some sort of bug? thanks -- bigbeer -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

9 years, 1 month

[opensuse-autoinstall] Repository Priority

by Tim Kirby

Repository Priority is obviously a useful thing to be able to manipulate. Yast lets me set it and zypper lets me set it. Yet, if I have multiple repositories defined at the beginning of my autoyast (including update repos so I get an up to date system built out of the box), I don't seem to have any control over the respective repository priorities - they're all defaulted. Or did I miss a subtle option somewhere? Tim -- Tim Kirby 651-605-9074 trk(a)cray.com Cray Inc. Information Systems -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

10 years

[opensuse-autoinstall] Identification of NICs by MAC address

by Sebastian Wenner

Hi, is there a way of identifying NICs by MAC address rather than by interface name? We have several multi-nic machines where we run into trouble with "normal" interface names. They have e.g. 4 onboard nics, powered by the bnx2 driver and an additional quad-port card powered by the e1000 driver. If the e1000 gets loaded before the bnx2, the first onboard (which is our usual link into the install network) comes up as eth4 instead of eth0. Identifying the adapter by its mac address would do a great job to avoid this confusion... Is there a way of specifying this in the autoyast file and at the boot prompt? Best regards Sebastian -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

10 years, 1 month

[opensuse-autoinstall] Partition/sector boundary alignment

by Paul

Hi, Can anyone suggest how to ensure AutoYAST creates partitions that are aligned to 4K boundaries? As far as I can tell, AY doesn't allow for specifying start sectors -- only by size. I understand that without such alignment the disk I/O subsystem will be worked harder than it needs to be in order to satisfy requests. My build will be SLES11sp1 on both physical and VMware. Thanks, -Paul -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

10 years, 2 months

[opensuse-autoinstall] opensuse 11.4 pxe installation - no repository in 'iso:/?iso=openSUSE-11.4-DVD-i586.iso&url=nfs://...

by Pierre Girard

Hello, I'm trying to install opensuse 11.4 and so far the machine loads pxe, starts initrd and linux, and starts the installation process. At some point it looks to add repositories and I get an error message saying there was a problem adding a repository. Here's the message from y2log: 2011-03-14 10:56:08 <1> client.example.com(3182) [YCP] Progress.ycp:599 Subprogress initialization skipped 2011-03-14 10:56:08 <3> client.example.com(3182) [YCP] Packages.ycp:1484 No repository in 'iso:/?iso=openSUSE-11.4-DVD-i586.iso&url=nfs://nfsserver.example.com/suse/o…' 2011-03-14 10:56:08 <1> client.example.com(3182) [Pkg] Packages.ycp:1063 Pkg Builtin called: LastError I checked the path, and I was able to manually mount the directory from one of the terminals without problem. Here's part of the pxelinux.cfg/default label workstation11.4-32 kernel linux11.4-32 append initrd=initrd11.4-32 ramdisk_size=65536 insmod=e100 textmode=1 autoyast=nfs://nfsserver.example.com/suse/autoyast-workstation-11.4 install=nfs://nfsserver.example.com/suse/opensuse/distribution/11.4/iso/ope… label manual11.4-32 kernel linux11.4-32 append initrd=initrd11.4-32 ramdisk_size=65536 manual=1 install='nfs://nfsserver.example.com/suse/opensuse/distribution/11.4/iso/openSUSE-11…' For now I'm trying to make the manual installation work. I have the same lines for opensuse 11.3 and 11.2 and those installations work correctly. Any idea what could be the problem? Thank you. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

10 years, 4 months

[opensuse-autoinstall] post-install reboot

by Swartz, Patrick H

Hi All, We are finally close to our final autoyast.xml configuration, but have a question about forcing one more reboot. One of the last scripts we run is to setup the atomic update partition and cloning, after we do this we need the system to reboot. I have tried just adding a reboot to this script, but that doesn't work - guessing because the script is never "complete" and the system continues to reboot. Patrick Swartz UNIX Planning & Engineering (DSUSSE) First Data 402-777-7337 desk 402-201-1192 Company cell 402-871-8981 Personal cell ----------------------------------------- The information in this message may be proprietary and/or confidential, and protected from disclosure. If the reader of this message is not the intended recipient, or an employee or agent responsible for delivering this message to the intended recipient, you are hereby notified that any dissemination, distribution or copying of this communication is strictly prohibited. If you have received this communication in error, please notify First Data immediately by replying to this message and deleting it from your computer. -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

10 years, 4 months

[opensuse-autoinstall] ssh service

by Gavin Reid

Greetings , i am attempting to have ssh start automatically after the install as finished vi autoyast on opensuse 11.4 however I cannot seem to make it function snipped from my autoyast : <runlevel> <default>3</default> <services config:type="list"> <service> <service_name>sshd</service_name> <service_status>enable</service_status> <service_start>3 5</service_start> <service_stop>3 5</service_stop> </service> </services> </runlevel> where am I going wrong ? -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

10 years, 4 months

[opensuse-autoinstall] relurl with SLES11 SP1

by Vladimir Ondrus

Hello, I have similar problem to http://lists.opensuse.org/opensuse-autoinstall/2010-10/msg00054.html. I am also using SLES11 SP1 Is relurl working with SLES11 SP1, or will work only with SLES11 SP2? I have this in autoyast.xml: <add-on> <add_on_products config:type="list"> <listentry> <media_url>relurl:///</media_url> <product>SuSE-Linux-Updates</product> <product_dir>updates</product_dir> <name>MyUpdates</name>  </listentry> </add_on_products> </add-on> here is my update repository: sles11sp1:/autoinst/ins_rep # l total 176 drwxr-xr-x 7 root root 4096 May 23 22:43 ./ drwxr-xr-x 7 root root 4096 May 23 22:19 ../ -rw-r--r-- 1 root root 9218 May 23 22:18 autoinst_noraid.xml -rw-r--r-- 1 root root 12006 May 23 22:18 autoinst_raid.xml -rw-r--r-- 1 root root 5314 May 23 22:43 autoinst_simple.xml dr-xr-xr-x 3 root root 4096 May 20 2010 boot/ -rw-r--r-- 1 root root 14457 May 23 22:19 content -rw-r--r-- 1 root root 197 May 23 22:19 content.asc -rw-r--r-- 1 root root 1710 May 23 22:19 content.key -r--r--r-- 1 root root 55168 May 12 2010 control.xml -r--r--r-- 1 root root 877 May 20 2010 gpg-pubkey-0dfb3188-41ed929b.asc -r--r--r-- 1 root root 1032 May 20 2010 gpg-pubkey-1d061a62-4bd70bfa.asc -r--r--r-- 1 root root 613 May 20 2010 gpg-pubkey-307e3d54-4be01a65.asc -r--r--r-- 1 root root 1694 May 20 2010 gpg-pubkey-3d25d3d9-36e12d04.asc -r--r--r-- 1 root root 938 May 20 2010 gpg-pubkey-7e2e3b05-4be037ca.asc -r--r--r-- 1 root root 1698 May 20 2010 gpg-pubkey-9c800aca-4be01999.asc -r--r--r-- 1 root root 1803 May 20 2010 gpg-pubkey-a1912208-446a0899.asc -r--r--r-- 1 root root 1348 May 20 2010 gpg-pubkey-b37b98a9-4be01a1a.asc drwxr-xr-x 2 root root 4096 May 23 19:19 media.1/ drwxr-xr-x 6 root root 4096 May 23 19:16 suse/ drwxr-xr-x 4 root root 4096 May 23 19:38 updates/ drwxr-xr-x 2 root root 4096 May 23 19:33 yast/ sles11sp1:/autoinst/ins_rep # find updates/ updates/ updates/SHA1SUMS updates/suse updates/suse/noarch ... updates/suse/noarch/SHA1SUMS updates/suse/setup updates/suse/setup/descr updates/suse/setup/descr/SHA1SUMS updates/suse/setup/descr/packages.en updates/suse/setup/descr/packages updates/suse/setup/descr/directory.yast updates/suse/setup/descr/packages.DU updates/directory.yast updates/media.1 updates/media.1/products updates/media.1/SHA1SUMS updates/media.1/media updates/media.1/directory.yast updates/content But when installing from this repository I have this in y2log: 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [YCP] clients/add-on_auto.ycp:20 ---------------------------------------- 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [YCP] clients/add-on_auto.ycp:21 add-on auto started 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [Pkg] clients/add-on_auto.ycp:170 Pkg Builtin called: SourceCreate 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [Pkg] PkgProgress.cc(_receiver):96 PkgReceiver progress: 0 (0%), running: true 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [Pkg] Source_Create.cc(createManagedSource):174 Original URL: relurl:///, product directory: ./updates 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [Pkg] Source_Create.cc(createManagedSource):180 Alias from URL: '' 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [Pkg] PkgFunctions.cc(CreateRepoManager):242 Path to repository files: /etc/zypp/repos.d 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [zypp] RepoManager.cc(init_knownRepositories):546 start construct known repos 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [zypp] RepoManager.cc(init_knownRepositories):567 end construct known repos 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [Pkg] Source_Create.cc(createManagedSource):215 Probing source type: 'relurl:///updates' 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [Pkg] PkgFunctions.cc(CreateRepoManager):242 Path to repository files: /etc/zypp/repos.d 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [zypp] RepoManager.cc(init_knownRepositories):546 start construct known repos 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [zypp] RepoManager.cc(init_knownRepositories):567 end construct known repos 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [zypp] RepoManager.cc(probe):1176 going to probe the repo type at relurl:///updates () 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [zypp++] MediaSetAccess.cc(rewriteUrl):385 Rewriting url relurl:///updates 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [zypp] MediaAccess.cc(open):110 Trying scheme 'relurl' 2011-05-23 16:44:34 <5> 219.1.90.86(3481) [zypp] Exception.cc(log):133 MediaAccess.cc(open):153 THROW: MediaAccess.cc(open):153: Unsupported URI schem e in 'relurl:///updates'. 2011-05-23 16:44:34 <5> 219.1.90.86(3481) [zypp] Exception.cc(log):133 2011-05-23 16:44:34 <5> 219.1.90.86(3481) [zypp] Exception.cc(log):133 RepoManager.cc(probe):1208 CAUGHT: MediaAccess.cc(open):153: Unsupported URI sch eme in 'relurl:///updates'. 2011-05-23 16:44:34 <5> 219.1.90.86(3481) [zypp] Exception.cc(log):133 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [zypp++] RepoManager.cc(probe):1209 problem checking for repodata/repomd.xml file 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [zypp++] MediaSetAccess.cc(rewriteUrl):385 Rewriting url relurl:///updates 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [zypp] MediaAccess.cc(open):110 Trying scheme 'relurl' 2011-05-23 16:44:34 <5> 219.1.90.86(3481) [zypp] Exception.cc(log):133 MediaAccess.cc(open):153 THROW: MediaAccess.cc(open):153: Unsupported URI schem e in 'relurl:///updates'. 2011-05-23 16:44:34 <5> 219.1.90.86(3481) [zypp] Exception.cc(log):133 2011-05-23 16:44:34 <5> 219.1.90.86(3481) [zypp] Exception.cc(log):133 RepoManager.cc(probe):1224 CAUGHT: MediaAccess.cc(open):153: Unsupported URI sch eme in 'relurl:///updates'. 2011-05-23 16:44:34 <5> 219.1.90.86(3481) [zypp] Exception.cc(log):133 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [zypp++] RepoManager.cc(probe):1225 problem checking for content file 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [zypp] MediaAccess.cc(open):110 Trying scheme 'relurl' 2011-05-23 16:44:34 <5> 219.1.90.86(3481) [zypp] Exception.cc(log):133 MediaAccess.cc(open):153 THROW: MediaAccess.cc(open):153: Unsupported URI schem e in 'relurl:///updates'. 2011-05-23 16:44:34 <5> 219.1.90.86(3481) [zypp] Exception.cc(log):133 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [zypp++] MediaSetAccess.cc(release):424 Releasing all media IDs held by this MediaSetAccess 2011-05-23 16:44:34 <5> 219.1.90.86(3481) [zypp] Exception.cc(log):133 RepoManager.cc(probe):1244 CAUGHT: MediaAccess.cc(open):153: Unsupported URI sch eme in 'relurl:///updates'. 2011-05-23 16:44:34 <5> 219.1.90.86(3481) [zypp] Exception.cc(log):133 2011-05-23 16:44:34 <5> 219.1.90.86(3481) [zypp] Exception.cc(log):133 RepoManager.cc(probe):1248 THROW: RepoManager.cc(probe):1248: Unknown error rea ding from 'relurl:///updates' 2011-05-23 16:44:34 <3> 219.1.90.86(3481) [Pkg] Source_Create.cc(SourceCreateEx):731 SourceCreate for 'relurl:///' product './updates' has failed 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [Pkg] PkgProgress.cc(_receiver):96 PkgReceiver progress: 0 (0%), running: true 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [Pkg] PkgProgress.cc(Done):84 Evaluating ProcessDone callback... 2011-05-23 16:44:34 <3> 219.1.90.86(3481) [YCP] Report.ycp:472 Failed to add add-on product. 2011-05-23 16:44:34 <1> 219.1.90.86(3481) [ui] YPushButton.cc(setFunctionKey):183 Guessing button role YOKButton for YPushButton "OK" at 0x34fe800 from f unction key F10 (END) Why relurl is not working? Regards, Vladimir Ondrus -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

10 years, 4 months

[opensuse-autoinstall] complete documentation

by Vladimir Ondrus

Hello, Where can I find a complete list of elements, which are possible inside networking section: I know that static ip address can be configured this way: <networking> <interfaces config:type="list"> <interface> <ipaddr>219.1.90.100</ipaddr> <netmask>255.255.255.128</netmask> </interface> But its not described in: http://www.suse.com/~ug/autoyast_doc/CreateProfile.Network.html Is there a link to old style autoyast documentation? Regards, Vladimir Ondrus -- To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org For additional commands, e-mail: opensuse-autoinstall+help(a)opensuse.org

10 years, 4 months

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

2005

2004

2003

2002

openSUSE Autoinstall May 2011