HPE Servers Gen10 Installation Kit SLES11 SP4

SUSE Linux Enterprise Server SLES Install-Boot
1
  1. Is there any documentation indicating the changes between v2 and v3 of the HPE Servers Gen10 Installation Kit for SLES11 SP4?
  2. When using an autoyast file that worked for SLES11 SP4 on HP G7, G8, and G9 hardware (for years) on a HP ML350 Gen10 server using the HPE Gen10 Installation Kit for SLES11 SP4 (from SUSE), the package resolver fails to locate all software packages in the autoyast file: specifically these packages are not installed as a result:
    kernel-source
    kernel-syms
    libxml2-python
    nfs_kernel_server
    wireshark
    ntp
    pure-ftp
    samba
    ulimit
    xinetd
    Was hoping there was some documentation to indicate why this is and some note indicating which software packages are not available for installation on a HP Gen10 hardware.
2

On 11/04/18 15:24, sdrake1 wrote:
[color=blue]

  1. Is there any documentation indicating the changes between v2 and v3
    of the HPE Servers Gen10 Installation Kit for SLES11 SP4?[/color]

Comparing version 2 and 3 installation information at
https://drivers.suse.com/hpe/HPE-Servers-Gen10/sle-11-sp4-x86_64/2.0/install-readme.html
and
https://drivers.suse.com/hpe/HPE-Servers-Gen10/sle-11-sp4-x86_64/3.0/install-readme.html
respectively, it looks like v3 adds support for the HPE system XL2x260W
Gen10 (Apollo W6000).

Ignoring the updated kernel-* packages v3 also adds elx-lpfc-kmp-,
lsi-megaraid_sas-kmp-, and xorg-x11-driver-video packages.
[color=blue]

  1. When using an autoyast file that worked for SLES11 SP4 on HP G7, G8,
    and G9 hardware (for years) on a HP ML350 Gen10 server using the HPE
    Gen10 Installation Kit for SLES11 SP4 (from SUSE), the package resolver
    fails to locate all software packages in the autoyast file: specifically
    these packages are not installed as a result:
    kernel-source
    kernel-syms
    libxml2-python
    nfs_kernel_server
    wireshark
    ntp
    pure-ftp
    samba
    ulimit
    xinetd
    Was hoping there was some documentation to indicate why this is and some
    note indicating which software packages are not available for
    installation on a HP Gen10 hardware.[/color]

With the exception of kernel-source all of the above packages should be
coming from regular SLES11 SP4 media as they’re not part of the
Installation Kit.

I think for any more information you’ll need to contact SUSE or HPE
directly.

HTH.

Simon
SUSE Knowledge Partner

If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.

3

It seems the packages I noted are actually installed - yast2 → software indicates so. I created this list by running autoyast and cloning the software config, writing out a autoinst.xml file and comparing the packages section to the autoinst.xml file I am using. So that is good, seems the packages and patterns are as desired. All of the above was with v2 of the HP Servers Install Kit.
Downloaded v3 of the HP Servers Install Kit and tried it - the install fails with a popup requesting that the HP Server Driver Kit be inserted. It refuses to accept the Hp Server Install Kit v3 or the SLES11 SP4 Install Media. Had to skip this error (it wanted to install kernel-default-devel). After the install completed, ran yast2–>repositories and it shows the Install Kit using the label Driver Kit…so it should have worked. Deleted this entry in the repository and added a new one, from DVD, and fed it my HP Servers Install Kit, it added it fine (using the name Drivers Kit).
Then ran yast2 and it installed the package it couldn’t find before.
V3 Install kit needs to be fixed.

4

But I still get the popup during installation that the Package Resolver Has Failed (without indicating what the problem package is). This times out in 10 seconds and the install continues - you miss it if you aren’t watching. Still don’t know what package is causing the trouble at this point.

5

The trouble was kernel-syms

Kernel-syms is not on the HPE Gen10 Driver Kit for SLES11 SP4. Removing it from autoinst.xml resolves the issue. After installation is complete, and SLES patches update the kernel, then kernel-syms can be installed if needed.

6

On 13/04/18 13:14, sdrake1 wrote:
[color=blue]

The trouble was kernel-syms

Kernel-syms is not on the HPE Gen10 Driver Kit for SLES11 SP4. Removing
it from autoinst.xml resolves the issue. After installation is
complete, and SLES patches update the kernel, then kernel-syms can be
installed if needed.[/color]

Thanks for the report back, I’m glad you found the cause. Are you not
providing the SLES11 SP4 Pool (and Updates) repo(s) during the
installation? If so, it should find and install the kernel-syms package.

HTH.

Simon
SUSE Knowledge Partner

If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.

7

No, not providing repos during the install because we have a different arrangement - we provide own patches after testing and release of patches that do not conflict with our software. So no registration or repos during install. This is done with our patch update after install. So, apparently, unattended install software list must not include packages that are not on the media. However, the only trouble is a popup that states the Package Resolver had a problem and if you aren’t watching you miss it - it times out in 10 sec and the installation continues. My unattended install file has false so I get no indication of what package is causing the trouble. Changing to true stops the install so the user must verify all the settings, at this point kernel-syms is indicated as the problem.

8

[QUOTE=smflood;52098]On 13/04/18 13:14, sdrake1 wrote:
[color=blue]

The trouble was kernel-syms

Kernel-syms is not on the HPE Gen10 Driver Kit for SLES11 SP4. Removing
it from autoinst.xml resolves the issue. After installation is
complete, and SLES patches update the kernel, then kernel-syms can be
installed if needed.[/color]

Thanks for the report back, I’m glad you found the cause. Are you not
providing the SLES11 SP4 Pool (and Updates) repo(s) during the
installation? If so, it should find and install the kernel-syms package.

HTH.

Simon
SUSE Knowledge Partner

If you find this post helpful and are logged into the web interface,
please show your appreciation and click on the star below. Thanks.
------------------------------------------------------------------------[/QUOTE]

I know this is a bit late, but i had the same issue on v4 of the kISO. The issue is that the kernel-syms requires kernel-trace-devel which is not included in the kISO. After modifying the kISO to include kernel-trave-devel version that matches kernel-syms, the error went away.