SLES 12 SP2 - Autoyast does not do second stage

SUSE Linux Enterprise Server SLES Install-Boot
1

Hi,

I’trying to use autoyast for SLES 12 SP2 installations. The VM PXE-boots
from ZCM 11.4 (Autoyast bundle), installation source is http (apache),
autoyast.xml comes from http too.

Everything works fine until reboot after the first stage. Then SLES simply
boots, without doing a second stage; consequently some settings are missing,
most obvious target “muti-user” is ignored and sshd is not running.

I found that in bootloader settings there are relicts from PXE booting,
kernel parameters include:

5 TFTPIP= PROXYADDR= PXEBOOT=YES

If I remove these manually on next reboot the second stage is executed.

I’m at a loss - whats going on here? Why these kernel parameters? Why do
they prevent stage 2? Do I miss something?

Thanks,
Mirko

2

Mirko,

It appears that in the past few days you have not received a response to your
posting. That concerns us, and has triggered this automated reply.

These forums are peer-to-peer, best effort, volunteer run and that if your issue
is urgent or not getting a response, you might try one of the following options:

Be sure to read the forum FAQ about what to expect in the way of responses:
http://forums.suse.com/faq.php

If this is a reply to a duplicate posting or otherwise posted in error, please
ignore and accept our apologies and rest assured we will issue a stern reprimand
to our posting bot…

Good luck!

Your SUSE Forums Team
http://forums.suse.com

3

Mirko Guldner wrote:
[color=blue]

Hi,

I’trying to use autoyast for SLES 12 SP2 installations. The VM PXE-boots
from ZCM 11.4 (Autoyast bundle), installation source is http (apache),
autoyast.xml comes from http too.

Everything works fine until reboot after the first stage. Then SLES simply
boots, without doing a second stage; consequently some settings are
missing, most obvious target “muti-user” is ignored and sshd is not
running.

I found that in bootloader settings there are relicts from PXE booting,
kernel parameters include:

5 TFTPIP= PROXYADDR= PXEBOOT=YES

If I remove these manually on next reboot the second stage is executed.

I’m at a loss - whats going on here? Why these kernel parameters? Why do
they prevent stage 2? Do I miss something?

Thanks,
Mirko[/color]

Found a file /srv/tftp/autoyast.cfg on my ZCM server, which contained:

DO NOT EDIT THIS FILE!

Modifying this file is unsupported and can have

unpredictable results on ZENworks Preboot Services

#======================================================#

ZENWORKSAPPEND 1
DEFAULT imaging
LABEL imaging
kernel $KERNEL
append 5 initrd=$INITRD install=$AUTOYAST_INSTALL
autoyast=$AUTOYAST_SCRIPT $KERNEL_PARMS

Removed the 5 from append, now it works. Don’t know where the 5 came from…