Quote Originally Posted by x0500hl View Post
Hi Malcolm,

I had checked that yesterday but neglected to post the output. There were 4 respositories for the SDK, with 2 enabled.

I resolved the issue so I don't think the output from 'zypper lr -d' will be relevant now.

Prior to SUSConnect there was a process that you needed to follow to re-register a server. The process included navigating to a certain directory, deleting certain files, etc. I thought of this while driving into the office this morning, so I did some more research.

The issue I had was that the SDK wasn't 'Activated'. The following is the command and output.
Code:
app-wfr23t-830:~ # SUSEConnect --list-extensions
AVAILABLE EXTENSIONS AND MODULES

    Advanced Systems Management Module 12 s390x
    Activate with: SUSEConnect -p sle-module-adv-systems-management/12/s390x

    Containers Module 12 s390x
    Activate with: SUSEConnect -p sle-module-containers/12/s390x

    Legacy Module 12 s390x (Activated)
    Deactivate with: SUSEConnect -d -p sle-module-legacy/12/s390x

    Public Cloud Module 12 s390x
    Activate with: SUSEConnect -p sle-module-public-cloud/12/s390x

    SUSE Linux Enterprise High Availability Extension 12 SP3 s390x
    Activate with: SUSEConnect -p sle-ha/12.3/s390x -r ADDITIONAL REGCODE

        SUSE Linux Enterprise High Availability GEO Extension 12 SP3 s390x
        Activate with: SUSEConnect -p sle-ha-geo/12.3/s390x -r ADDITIONAL REGCODE

    SUSE Linux Enterprise Server LTSS 12 SP3 s390x
    Activate with: SUSEConnect -p SLES-LTSS/12.3/s390x -r ADDITIONAL REGCODE

    SUSE Linux Enterprise Software Development Kit 12 SP3 s390x
    Activate with: SUSEConnect -p sle-sdk/12.3/s390x

    SUSE Manager Server 3.0 s390x
    Activate with: SUSEConnect -p SUSE-Manager-Server/3.0/s390x -r ADDITIONAL REGCODE

    SUSE Manager Server 3.1 s390x
    Activate with: SUSEConnect -p SUSE-Manager-Server/3.1/s390x -r ADDITIONAL REGCODE

    SUSE Manager Server 3.2 s390x
    Activate with: SUSEConnect -p SUSE-Manager-Server/3.2/s390x -r ADDITIONAL REGCODE

    SUSE Package Hub 12 SP3 s390x
    Activate with: SUSEConnect -p PackageHub/12.3/s390x

    Toolchain Module 12 s390x
    Activate with: SUSEConnect -p sle-module-toolchain/12/s390x

    Web and Scripting Module 12 s390x
    Activate with: SUSEConnect -p sle-module-web-scripting/12/s390x


REMARKS

(Not available) The module/extension is not enabled on your RMT/SMT
(Activated)     The module/extension is activated on your system

MORE INFORMATION

You can find more information about available modules here:
https://www.suse.com/products/server/features/modules.html
You can see that the entry for "SUSE Linux Enterprise Software Development Kit 12 SP3 s390x" is not immediately following by 'Activated' like the entry for "Legacy Module 12 s390x". The command to activate is right under the Extension name.

Here is the command and output:
Code:
app-wfr23t-830:~ # SUSEConnect -p sle-sdk/12.3/s390x
Registering system to SUSE Customer Center

Updating system details on https://scc.suse.com ...

Activating sle-sdk 12.3 s390x ...
-> Adding service to system ...
-> Installing release package ...

Successfully registered system
After this the 'zypper patch' command ran successfully.

I hope that this helps someone else.


Harley
Hi
Yes, that's where I was heading to Thanks for the feedback and good to see you back on track