Anonymous_User Absent Member.
Absent Member.
692 views

autoyast bundle, autoyast.cfg, SLES 12

Hi,

we have prepared an autoyast installation for SLES 12; everything works
fine, but there was a problem, that I'd like to understand better:

The second stage of the autoyast installation did not run; after reboot the
system just booted, without executing that second stage. I found that this
was because of a "kernel parameter" "5" in the bootloader configuration;
this caused the system to boot into GUI mode and not to execute the
installation. If I removed that "5" and rebooted, the second stage was
executed.

I then found that the "5" comes from autoyast.cfg on the imaging server:


#====================== WARNING! ======================#
# 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



Removing the number there solves the problem.


But besides that its unsupported to edit this file, I don't understand it:
why is the "5" there and why are these parameters passed into the
configuration of the *deployed* system, instead of the *imaging* system
only?

Autoyast installation fails without editing this file, so what's the
"supported" way to do this?

Thanks,
Mirko


Labels (2)
0 Likes
5 Replies
Micro Focus Expert
Micro Focus Expert

Re: autoyast bundle, autoyast.cfg, SLES 12

I would recommend an SR.
I'm not sure you will find anyone here that knows the answer.....

Keep in Mind, I'm FAR from a Linux Expert and what I'm going to say is a 100% Complete and Total GUESS.
The Imaging Server can answer DHCP INFORM Requests, which a device can send out.
(These can occur even on static IP systems to request additional system info.)
I will guess that the Linux may be sending such a request and the Imaging Server is answering.

This seems to indicate I may be partially correct.....
https://www.suse.com/documentation/sles-12/book_autoyast/data/invoking_autoinst.html

My Guess is you have found the answer and I would just go with it.

However, an SR would be recommended....perhaps the defaults for that file are not the best.
But I'm the furthest thing from a Linux Person.....


Mirko Guldner;2470531 wrote:
Hi,

we have prepared an autoyast installation for SLES 12; everything works
fine, but there was a problem, that I'd like to understand better:

The second stage of the autoyast installation did not run; after reboot the
system just booted, without executing that second stage. I found that this
was because of a "kernel parameter" "5" in the bootloader configuration;
this caused the system to boot into GUI mode and not to execute the
installation. If I removed that "5" and rebooted, the second stage was
executed.

I then found that the "5" comes from autoyast.cfg on the imaging server:


#====================== WARNING! ======================#
# 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



Removing the number there solves the problem.


But besides that its unsupported to edit this file, I don't understand it:
why is the "5" there and why are these parameters passed into the
configuration of the *deployed* system, instead of the *imaging* system
only?

Autoyast installation fails without editing this file, so what's the
"supported" way to do this?

Thanks,
Mirko
0 Likes
Micro Focus Expert
Micro Focus Expert

Re: autoyast bundle, autoyast.cfg, SLES 12

If you make an SR...please post here or Private Message me....
I find this subject quite interesting!!!!
0 Likes
Anonymous_User Absent Member.
Absent Member.

Antw: Re: autoyast bundle, autoyast.cfg, SLES 12


Thanks for your answer and sorry for my delayed reply.

I am not sure, if I completely understand your idea... this is an
explanation how the installation system gets the information, isn't it? But
it does not explain why this value is taken over persistently in bootloader
configuration of the deployed system - or did I miss something? Btw: there
is also TFTPIP=.... PROXYADDR=0.0.0.0 PXEBOOT=YES persistent in bootloader
configration - but these parameters doesn't seem to do any harm, in contrast
to that "5".

I'll open an SR.

Thanks,
Mirko


>>>


> I would recommend an SR.
> I'm not sure you will find anyone here that knows the answer.....
>
> Keep in Mind, I'm FAR from a Linux Expert and what I'm going to say is a
> 100% Complete and Total GUESS.
> The Imaging Server can answer DHCP INFORM Requests, which a device can
> send out.
> (These can occur even on static IP systems to request additional system
> info.)
> I will guess that the Linux may be sending such a request and the
> Imaging Server is answering.
>
> This seems to indicate I may be partially correct.....
>

https://www.suse.com/documentation/sles‑12/book_autoyast/data/invoking_au

> toinst.html
>
> My Guess is you have found the answer and I would just go with it.
>
> However, an SR would be recommended....perhaps the defaults for that
> file are not the best.
> But I'm the furthest thing from a Linux Person.....
>
>
> Mirko Guldner;2470531 Wrote:
>> Hi,
>>
>> we have prepared an autoyast installation for SLES 12; everything works
>> fine, but there was a problem, that I'd like to understand better:
>>
>> The second stage of the autoyast installation did not run; after reboot
>> the
>> system just booted, without executing that second stage. I found that
>> this
>> was because of a "kernel parameter" "5" in the bootloader
>> configuration;
>> this caused the system to boot into GUI mode and not to execute the
>> installation. If I removed that "5" and rebooted, the second stage was
>> executed.
>>
>> I then found that the "5" comes from autoyast.cfg on the imaging
>> server:
>>
>>
>> #====================== WARNING! ======================#
>> # 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
>>
>>
>>
>> Removing the number there solves the problem.
>>
>>
>> But besides that its unsupported to edit this file, I don't understand
>> it:
>> why is the "5" there and why are these parameters passed into the
>> configuration of the *deployed* system, instead of the *imaging* system
>> only?
>>
>> Autoyast installation fails without editing this file, so what's the
>> "supported" way to do this?
>>
>> Thanks,
>> Mirko


0 Likes
Micro Focus Expert
Micro Focus Expert

Re: Antw: Re: autoyast bundle, autoyast.cfg, SLES 12

It is persistent, because the value is delivered to the Linux System via DHCP Inform Request responses given to the Linux System from the Imaging Server.

DHCP can deliver far more information than just IP, Gateway, and DNS Server info.
For Linux, AutoYas behavior is controllable too.....
0 Likes
Anonymous_User Absent Member.
Absent Member.

Antw: Re: autoyast bundle, autoyast.cfg, SLES 12

I had opened a SR. The Technical Support Engineer confirmed that it's ok to
change the autoyast.cfg and that this needs to be documented. So far I got
no information about the "why", so I still don't know why parameters in
this file affect the bootloader configuration of the autoyast-installed
system.

Regards,
Mirko


>>>


> If you make an SR...please post here or Private Message me....
> I find this subject quite interesting!!!!


0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.