Migrate_SLES_to_SLES-for-SAP-12.sh on Power issue?????

:mad: Hi All
I perform a "Migrating a SLES 12 SP1 for POWER LE system to SLES for SAP Applications for POWER LE 12 SP1" using the dedicated script.
a) the script finish withour errors = success
b) but the commande "zypper list" shows :
# zypper lr
# | Alias | Name | Enabled | GPG Check | Refresh
--+
+
+
+
+
1 | SLES12-SP1-12.1-0 | SLES12-SP1-12.1-0 | Yes | (r ) Yes | No

and not SLES for SAP expected.

Question : who can tell me what's wrong and why????
please help!!!!

Comments

  • BoubadBoubad Member
    please find herein the trace of the script... it may be helpfull:

    Please enter the https URL to the SMT server
    Example: https://mysmt.corp.com:

    + read SMT_URL
    https://smtproxy.wdf.sap.corp
    + wget --no-verbose -q --no-check-certificate --dns-timeout 10 --connect-timeout 10 --output-document /tmp/smt.crt https://smtproxy.wdf.sap.corp/smt.crt
    + ''
    + wget --no-verbose -q --no-check-certificate --dns-timeout 10 --connect-timeout 10 --output-document /tmp/clientSetup4SMT.sh https://smtproxy.wdf.sap.corp/repo/tools/clientSetup4SMT.sh
    + chmod +x /tmp/clientSetup4SMT.sh
    ++ openssl x509 -in /tmp/smt.crt -fingerprint
    ++ grep '^SHA1 Fingerprint='
    ++ cut -d= -f2
    + FINGERPRINT=0.......
    + ''
    + ''
    + /tmp/clientSetup4SMT.sh https://smtproxy.wdf.sap.corp/center/regsvc --fingerprint 0......C --yes
    + /usr/sbin/SUSEConnect -p SLES_SAP/12.1-0/ppc64le --url https://smtproxy.wdf.sap.corp
    + rpm -e --nodeps sles-release
    + echo -e '\nExchanging release packages...\n'

    Exchanging release packages...

    + zypper -n install -f SLES_SAP-release sles-release
    + rpm -e sles-release-DVD
    + cp /etc/default/grub /etc/default/grub-SLES12
    + sed s/SLES12/SLES_SAP-12/ -i /etc/default/grub
    + /sbin/update-bootloader --reinit
    + ''
    + ''
    + for i in '/etc/zypp/repos.d/SUSE_Linux_Enterprise_Server_12_SP1_${ARCH}*'
    + ''
    + rm -f /tmp/smt.crt /tmp/clientSetup4SMT.sh
    + echo -e '\nYou'\''re now subscribed to following channels:\n'

    You're now subscribed to following channels:

    + zypper lr
    Warning: The /etc/products.d/baseproduct symlink is dangling or missing!
    The link must point to your core products .prod file in /etc/products.d.

    # | Alias | Name | Enabled | GPG Check | Refresh
    --+
    +
    +
    +
    +
    1 | SLES12-SP1-12.1-0 | SLES12-SP1-12.1-0 | Yes | (r ) Yes | No
  • BoubadBoubad Member
    No I'm not looking for package but a shared experience beedback regarding such a scripot execution!


    regards
  • Jens-U.Jens-U. Knowledge Partner
    ah, ok, the trace looked so familiar (it was in #4 of the referenced thread)

    Maybe you could open a service request - that warning about the dangling symlink doesn't sound healthy to me (but I've not used SLES on Power before, so I cannot tell what's up with that). Out of curiosity, how does that part look when using "ls -l /etc/products.d"?

    Oh, and BTW - you might want to check if SUSEConnect generated any logs and if so, what's in there. That's the step where the new repositories would have been added, but I see none of that.

    What's in /etc/zypp/repos.d/ ? the script looks for i.e. /etc/zypp/repos.d/SUSE_Linux_Enterprise_Server_12_SP1_ppc64le* but seems to find none of that - what's the name of the current repo file there (which is what zypper lr reports at the end of the script run)?

    Regards,
    J
  • BoubadBoubad Member
    Hi

    here is the results of the following command after executing the migration script:

    # ls -l /etc/products.d
    total 128
    -rw-r--r-- 1 root root 2699 Nov 26 2015 SLES.prod-old-13-06
    lrwxrwxrwx 1 root root 9 May 28 12:32 baseproduct -> SLES.prod

    # ls -l /etc/zypp/repos.d/
    total 64
    -rw-r--r-- 1 root root 132 Jun 6 14:27 SLES12-SP1-12.1-0.repo

    # zypper lr
    Warning: The /etc/products.d/baseproduct symlink is dangling or missing!
    The link must point to your core products .prod file in /etc/products.d.

    # | Alias | Name | Enabled | GPG Check | Refresh
    --+
    +
    +
    +
    +
    1 | SLES12-SP1-12.1-0 | SLES12-SP1-12.1-0 | Yes | (r ) Yes | No


    Yes after executing the script,
    - we lost the SLES.prod file

    - the repo expected by the scipt is not find as shown above!!!

    ?????????? thanks for your support!!

    NB: after the installation of the SLES and before applying the script, the repo is : rw-r--r-- 1 root root 132 May 28 09:41 SLES12-SP1-12.1-0.repo
  • BoubadBoubad Member
    on top of that .... the command "zypper product" return:
    # zypper products
    Loading repository data...
    Reading installed packages...
    S | Repository | Internal Name | Name | Version | Arch | Is Base
    --+
    +
    +
    +
    +
    +
    i | @System | SLES | SUSE Linux Enterprise Server 12 SP1 | 12.1-0 | ppc64le | Yes
  • abea_2017abea_2017 New or Quiet Member
    what is the procedure to upgrade the kernel rpms in suse, we currently have this kernel revision installed:

    rpm -qa | grep kernel
    kernel-default-4.4.21-69.1.x86_64
    nfs-kernel-server-1.3.0-26.3.x86_64
    kernel-macros-4.4.21-69.1.noarch
    kernel-default-devel-4.4.21-69.1.x86_64
    kernel-devel-4.4.21-69.1.noarch
    kernel-firmware-20160516git-17.6.noarch
    kernel-source-4.4.21-69.1.noarch
    kernel-syms-4.4.21-69.1.x86_64

    new proposed kernel: kernel-default-4.4.59-92.17

    thank you
  • BoubadBoubad Member
    HI
    It's not my question.... I want to understand why the official migration script for SLES 12 SP1 on POwer system for HANA will not end with the updated label of the SUSE.... "SLES for SAP...."

    regards
    Bouba
  • Jens-U.Jens-U. Knowledge Partner
    Hi,
    Boubad wrote: »
    Hi

    here is the results of the following command after executing the migration script:

    # ls -l /etc/products.d
    total 128
    -rw-r--r-- 1 root root 2699 Nov 26 2015 SLES.prod-old-13-06
    lrwxrwxrwx 1 root root 9 May 28 12:32 baseproduct -> SLES.prod

    it might be interesting to see when the product file was renamed - have a look at the directory timestamp ("ls -ld /etc/products.d") to see if it was last modified before you started the migration. Maybe the "base setup" isn't what the migration script requires. (That "dangling symlink" by itself is already something that will need fixing - the results from "zypper products" probably stems from zypper taking *any* file from that directory - "baseproduct" is invalid and thus skipped, "SLES.prod-old-13-06" has valid content and points to the non-SLES variant).

    > I want to understand why the official migration script for SLES 12 SP1 on POwer system for HANA will not end with the updated label of the SUSE.... "SLES for SAP...."

    If everything else fails - open a service request to get engineering support...

    Regards,
    J
Sign In or Register to comment.