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!
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
Hi,
here's the problems I ran into. They all seem to be related to
systemd, but I did not want to hijack the other thread, although this
one might solve the other problem, too.
1. The final kexec/reboot is not executed. Both
<final_reboot config:type="boolean">false</final_reboot>,
meaning kexec will be used, and
<final_reboot config:type="boolean">true</final_reboot>
have no effect at all[0]. This also means that...
2. Init-Services (<runlevel>) defined in autoyast are not
started/stopped, so, f.e., no ssh keys are generated. (This also
results in a lot of subsequent errors in our setup.)
To fix this, just include:
<software>
<remove-packages config:type="list">
<package>systemd-sysvinit</package>
</remove-packages>
</software>
This way, sysvinit-init will be installed and used.
When can we expect autoyast to support systemd?
[0]: Once you do a manual reboot (if you happen to have access other
than ssh to the machine), the machine will do the autoyast
kexec/reboot after that.
--
Kind regards/Mit freundlichen Grüßen
Christopher 'm4z' Holm
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org
Hi,
I want to upgrade a couple of HPC nodes. All working in a
private subnet. To get access to some additional repositories
I need a proxy config. But when I add the proxy and proxyport
statement at the pxe server for the (test) node, the autoyast
file is not found. Without the proxy statements the autoyast file
is found, but many packages are not found ;(
I've tested the proxy using wget and everything is working from
the cli. Any idea what's wrong or howto debug ?
LABEL install
KERNEL kernel
APPEND initrd=initrd showopts
install=nfs://192.168.1.100/Net/Groups/Services/LNX_FTP/INSTALL/sles11SP1/x86_64/
autoyast=http://192.168.1.100/sysinst/autoyast/node25 textmode=1
netdevice=eth0 dhcp=1 proxy=192.168.1.100 proxyport=3128
-> no autoyast found
APPEND initrd=initrd showopts
install=nfs://192.168.1.100/Net/Groups/Services/LNX_FTP/INSTALL/sles11SP1/x86_64/
autoyast=http://192.168.1.100/sysinst/autoyast/node25 textmode=1
netdevice=eth0 dhcp=1
-> autoyast found, no external sources ...
--
Thanks and bye,
Peer
_________________________________________________________
Max-Planck-Institut fuer Biogeochemie
Dr. Peer-Joachim Koch
Hans-Knöll Str.10 Telefon: ++49 3641 57-6705
D-07745 Jena Telefax: ++49 3641 57-7705
During my 12.1 bughunt, I (re-)encountered some inconsistencies that
I've been wanting to ask (and nag) about since I started working with
autoyast a few years back, and a few new ones:
1. autoyast generates a lot of messages.
For an autoyast dev, this might be wonderful, but dumb users like
myself are simply lost in tens of thousands of messages. It makes
finding errors in the logs really hard, especially when you don't know
what string(s) you're looking for.
It would be great if there was, for example, an additional
warnings-and-errors-only log.
2. autoyast generates a lot of "noise" in diffs.
When cloning a system with yast or editing it manually and then
running it through yast again to check for errors, yast changes the
profile in various ways. This makes it sometimes harder to see the
"real" differences. (In general, one could say everything is fine
because the inconsistencies below all "converge" towards a final
state, but nevertheless I sometimes wonder why these things happen.)
2.a) (this is new in 12.1 and did not happen before:) for some reason
the DNS settings are not kept for stage 2, so I need this script in
12.1:
<script>
<debug config:type="boolean">true</debug>
<feedback config:type="boolean">false</feedback>
<filename>fixresolv</filename>
<interpreter>shell</interpreter>
<network_needed config:type="boolean">true</network_needed>
<source><![CDATA[resolv=$(cat /etc/resolv.conf)
if [ -z "$resolv" ]; then
echo "# resolv.conf was empty, ftfy.
nameserver a.b.c.d" >> /etc/resolv.conf
fi
]]></source>
</script>
2.b) <keep_install_network> is _always_ deleted by yast.
2.c) even though a <runlevel> section exists, the package
yast2-runlevel is not automatically installed.
2.d) even though mail settings (aliases, mailrelay) exist, the package
yast2-mail is not automatically installed.
2.e) When *cloning* an existing system, I see inconsistent and
sometimes non-helpful behavior. What happens is that for certain
settings (see below), there are different cases that can happen:
1. tag doesn't exist vs.
2. tag exists but is empty vs.
3. tag exists with default/cloned value
Of these three, only the last one is really helpful because I can
actually see what value the cloned machine had set. Some of the
settings where I have seen this in 12.1 are:
<languages>, <filesystem_id>, <partition_id>,
<displaymanager_shutdown>,
<displaymanager_xserver_tcp_port_6000_open>, <run_updatedb_as>,
<hibernate_system>, <smtpd_listen_remote>, <dhclient_client_id>,
<nss_base_{passwd,group,shadow}>.
I have only had my eye really close on the <password_settings>
section, the behavior was like this:
* random existence of default value or empty tag (this happened
for both the complete section or parts of it, depending on which parts
of it were set to the default on the cloned machine)
* if it did exist with empty values, yast (sometimes) deletes
(some of!) those tags
* if it did not exist, yast (sometimes) inserts (some of!) those
tags with the default (non-empty) values (but *only* if the whole
<password_settings> did not exist. if only parts are missing, these
are not inserted)
In the two former cases (no tag/empty tag), the user has to remove
them from the profile, run it through yast again, and only then will
the values appear (or it will not be added again by yast and wasn't so
important anyway).
2.f) While the sections in the profile seem to be sorted alphabetically by yast,
1. the order of <users> seems to be random,
2. the order of the <*packages> and <*patterns> sections seems to
be nonrandom, but isn't nonalphabetic either.
Does the order of these sections matter? If not, could the please be
sorted deterministically (alphabetically, or, f.e., in order of UIDs
for the users)? Right now, when comparing different profiles, the user
has to do a lot of "merging" first before he/she can see the real
differences.
It would be really great if the debugging possibilites in autoyast
would be improved. They've been a source of frustration to me over the
last weeks.
That all sounds so negative. Let me end with a big thank you to all
contributors: Thank you. autoyast saves me a lot of time. (:
--
Kind regards
686f6c6d / Christopher 'm4z' Holm
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org
Hi,
maybe time to start with beta tests? :)
For a quick overview of the openSUSE Roadmap, please see:
http://en.opensuse.org/Roadmap
--
ciao, Uwe Gansert
SUSE LINUX Products GmbH, HRB 16746 (AG Nürnberg)
GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer
Home: http://www.suse.de/~ug - Blog: http://suse.gansert.net
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org
Novell KB Document 3594167 "Howto: Configure Multipath (MPIO) to boot from SAN"
http://www.novell.com/support/viewContent.do?externalId=3594167&sliceId=1
describes the process to set up boot from SAN after a server has been installed. Is it possible to do all or most of this configuration during installation via autoyast profile?
or is it a lot easier to do "normal" install and follow TID above to change menu.lst and /etc/fstab files.
Thanks in advance,
Nefi M.
Hello Everyone,
short question. The new features, documented on
http://suse.gansert.net/?p=239
'Unattended Upgrade with AutoYaST'
Is this feature available when we upgrade the system not via reboot an
CD but upgrading it during the running os with calling yast on cli?
Regards
Ruediger
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org
Dear AutoYaST crew ,
we have been using AutoYaST for installation of the last openSUSE
distributions,
but with 12.1 the unattended installation doesn't succeed anymore.
The installation runs as usual with installing packages and writing
system configuration.
But at the end , shutting down is incomplete
The last messages i see are:
Es wird versucht , den installierten kernel mit kexec zu laden. Bitte warten
Shutting down Name Service Cache Daemon Done
On different clients the language was german or english.
Then I see a black monitor with a colourful suse-green stripe at top
and in the middle .
Then the system hangs (even over night)
If I do a manual hard shutdown and boot , the system comes up ( with
trans replayed) with
Kernel 3.1.0-1.2-desktop Asparagus
and i see the known welcome window and "all seems right" .
Our post.sh script was completely executed.
To Prevent the hanging
I looked for several workarounds for my XML-File , which was working
fine for 11.3
1)
<general>
<mode>
<confirm config:type="boolean">false</confirm>
<reboot config:type="boolean">true</reboot>
</mode>
</general>
I inserted
a) <final_halt config:type="boolean">true</final_halt>
--> same effect
b) <halt config:type="boolean">false</halt>
<forceboot
config:type="boolean">true</forceboot> --> same effect
c) <final_reboot
config:type="boolean">true</final_reboot> --> same effect
2) I included:
<software> <remove-packages config:type="list">
<package>systemd-sysvinit</package>
</remove-packages>
</software>
--> same effect
3) <chroot-scripts config:type="list">
<script>
<chrooted config:type="boolean">true</chrooted>
<interpreter>shell</interpreter>
<source><![CDATA[
insserv autoyast
]]></source>
</script>
</chroot-scripts>
--> same effect
4 ) Some packages are explicitly added:
<package>yast2-schema</package>
<package>autoyast2</package>
<package>yast2-slp</package>--> same effect
<package>yast2-bootloader</package>
<package>kexec-tools</package>
--> same
effect
5) I appended the boot-option for autointall
ipv6.disable=1
--> same effect
With the following boot-Options for Yast
textmode=1 TERM=xterm
the last operations are
Master Record Control : switching to runlevel 5
.... Running
/etc/init.d/before.local done
Starting acpid
Loading CPUFreq modules and system hangs over
night
Any help is appreciated.
Marianne Frerichs
------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
Forschungszentrum Juelich GmbH
52425 Juelich
Sitz der Gesellschaft: Juelich
Eingetragen im Handelsregister des Amtsgerichts Dueren Nr. HR B 3498
Vorsitzender des Aufsichtsrats: MinDir Dr. Karl Eugen Huthmacher
Geschaeftsfuehrung: Prof. Dr. Achim Bachem (Vorsitzender),
Karsten Beneke (stellv. Vorsitzender), Prof. Dr.-Ing. Harald Bolt,
Prof. Dr. Sebastian M. Schmidt
------------------------------------------------------------------------------------------------
------------------------------------------------------------------------------------------------
Kennen Sie schon unsere app? http://www.fz-juelich.de/app
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org