I recently noticed that an autoyast installation of SLES 12 SP3 did not show the the SDK as being installed (in the output of ‘zypper search -t product’), despite it being present in my profile, and 'SUSEConnect --list-extensions' reported it as registered but not installed. Running ‘zypper install sle-sdk-release’ or ‘zypper in -t product sle-sdk’ afterwards will then mark it as installed.
Further testing revealed this to be the case in SP2 also, but for SLES 12 SP1, the sle-sdk product *is* still automatically installed.
I have had the mounted SLE SDK ISO listed as an add-on in my profile for many versions (going back to SLES 11 GA, I believe) much like this:
====
<add-on>
<!-- remember to also register add-ons under suse_register -->
<add_on_products config:type="list">
<listentry>
<media_url>http://rgs-install.local/mounts/sles12/sp2/sdk1/</media_url>
<product>sle-sdk</product>
<product_dir>/</product_dir>
<alias>SLE-SDK12-SP2</alias>
</listentry>
</add_on_products>
</add-on>
====
And up through SLES 12 SP1, everything was fine.
For all SP versions, I see in the YaST logs stuff like this:
2017-10-24 15:42:44 <1> dhcp-116(3246) [zypp++] PoolItem.cc(setBuddy):168 U__s_(9458)product:sle-sdk-12.2-0.x86_64(SLE-SDK12-SP2) has buddy U__s_(7684)sle-sdk-release-12.2-1.124.x86_64(SLE-SDK12-SP2)
...but for some reason SP2/SP3 don’t automatically install sle-sdk-release any more.
Adding it to <packages>, either 'sle-sdk-release', or 'product:sle-sdk', is a suitable workaround, but I wonder what changed?
====
<software>
<packages config:type="list">
<package>mlocate</package>
<!-- <package>... -->
<!-- pick one of these, they are equivalent: -->
<package>product:sle-sdk</package>
<package>sle-sdk-release</package>
</packages>
<patterns config:type="list">
<pattern>Minimal</pattern>
<pattern>base</pattern>
</patterns>
<!--
Based on the schema file, this should work, but it does not:
<products>
<product>sle-sdk</product>
</products>
-->
</software>
====
Andrew Daugherity
Senior Systems Administrator
Division of Research, Texas A&M University
Am 10/05/2017 um 09:55 AM schrieb Daniel Spannbauer:
> Hello,
>
>
> after solving my efi-case I struggle with another problem.....
>
> I create an Iso-Image for our stuff which they can download and install
> opensuse to their machines.
>
> They can burn the ISO on a DVD or create a usb-stick from that iso.
>
> Booting is working from both. But I have only one grub.cfg. So, how to
> tell the opensuse installation system the correct path to the repo and
> the autoinst-xml-file?
>
> At the moment I try it with:
>
> install=disk:/?device=*label/inst_14_*
> autoyast2=disk:/?device=*label/inst_14_*/autoinst.xml
>
> The ISO and the USB stick are labled with "inst_14_??" where ?? is a
> version number.
>
> But the installation process can't find the installation source, doesn't
> matter If I boot from USB oder DVD.
Is there no parameter to set the location of the autoinst-file for bot,
DVD and USB?
file:///autionst.xml is only working on DVD, not on a pen drive,
device:/// is only working on a pen drive but not on a DVD...
Regards
Daniel
--
Daniel Spannbauer Systemadministration
marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11
Rechbergstr. 4-6, D 87727 Babenhausen Mobil +49 171 4033220
http://www.marco.de/ Email ds(a)marco.de
Geschäftsführer Martin Reuter HRB 171775 Amtsgericht München
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org
> Hello Johannes,
>
> I've looked over the help of mksusecd. It seems to do automatically what
> I did by my own script.
> But:
> - I have modified isolinux.cfg which special boot entrys for different
> hardware. Same for the grub2. Are they overwritten when I use mksusecd?
> - The content is signed with a gpg key which is protected by a
> passphrase. With my script I use gpg via batchmode and it gets the
> passphrase from a textfile. Does mksusecd support that scenario?
> - mksusecd need root privilegs, my script runs as user.
>
> That are the stumbling blocks I figured out till now.
> Who is the maintainer of that script? Looks great so far.
>
Ok, holidys are over...tried the mksusecd deeper....
When installing from the installation media created with mksusecd i get
an error from Autoyast:
"No base products found"......
Any idea what autoyast is missing here?
Regards
Daniel
--
Daniel Spannbauer Systemadministration
marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11
Rechbergstr. 4-6, D 87727 Babenhausen Mobil +49 171 4033220
http://www.marco.de/ Email ds(a)marco.de
Geschäftsführer Martin Reuter HRB 171775 Amtsgericht München
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org
Hello,
after solving my efi-case I struggle with another problem.....
I create an Iso-Image for our stuff which they can download and install
opensuse to their machines.
They can burn the ISO on a DVD or create a usb-stick from that iso.
Booting is working from both. But I have only one grub.cfg. So, how to
tell the opensuse installation system the correct path to the repo and
the autoinst-xml-file?
At the moment I try it with:
install=disk:/?device=*label/inst_14_*
autoyast2=disk:/?device=*label/inst_14_*/autoinst.xml
The ISO and the USB stick are labled with "inst_14_??" where ?? is a
version number.
But the installation process can't find the installation source, doesn't
matter If I boot from USB oder DVD.
Any hints?
Regards
Daniel
--
Daniel Spannbauer Systemadministration
marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11
Rechbergstr. 4-6, D 87727 Babenhausen Mobil +49 171 4033220
http://www.marco.de/ Email ds(a)marco.de
Geschäftsführer Martin Reuter HRB 171775 Amtsgericht München
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org
Hello,
I try to create a UEFI-Bootable Iso-Image.
The "normal" Iso is working fine, but on a UEFI-Only machine the burned
DVD is not found.
But how do I generate a UEFI Iso-Image on Leap? genisoimage seems to
lack the parameter --eltorito-boot
Regards
Daniel
--
Daniel Spannbauer Systemadministration
marco Systemanalyse und Entwicklung GmbH Tel +49 8333 9233-27 Fax -11
Rechbergstr. 4-6, D 87727 Babenhausen Mobil +49 171 4033220
http://www.marco.de/ Email ds(a)marco.de
Geschäftsführer Martin Reuter HRB 171775 Amtsgericht München
--
To unsubscribe, e-mail: opensuse-autoinstall+unsubscribe(a)opensuse.org
To contact the owner, e-mail: opensuse-autoinstall+owner(a)opensuse.org