SMT Server Self Registration not working with SCC

This document (7018583) is provided subject to the disclaimer at the end of this document.

Environment

SUSE Linux Enterprise Server 11 Service Pack 3 (SLES 11 SP3)
SUSE Linux Enterprise Server 11 Service Pack 4 (SLES 11 SP4)
SUSE Linux Enterprise Server 12 Service Pack 1 (SLES 12 SP1)
SUSE Linux Enterprise Server 12 Service Pack 2 (SLES 12 SP2)

Situation

On a SMT (Subscription Management Tool) server configured to access SCC (SUSE Customer Center), when registering a Client against the SMT server or when running the SMT daily registration update to SCC, the procedure fails with an "Error 404" message.

Resolution

To solve this issue, the Operating System of the SMT server should be de-registered and then re-registered directly against SCC (not against itself), by following the steps in TID # 3303599

Once the re-registration of the Operating System is finished, run the following commands:

# smt-register --reseterror

# smt-sync

After this on the Client run the registration against SMT one more time.

Cause

The SCC protocol defines that the Server (SCC or SMT) defines the credentials and not the Client. Every initial registration create new credentials and SCC requires to 'know' the SMT server to allow it to send data. This means SMT must be registered against SCC directly.

Disclaimer

This Support Knowledgebase provides a valuable tool for SUSE customers and parties interested in our products and solutions to acquire information, ideas and learn from one another. Materials are provided for informational, personal or non-commercial use within your organization and are presented "AS IS" WITHOUT WARRANTY OF ANY KIND.