OES 2023 does not sync in SUSE Manager

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

Environment

SUSE Manager 4.3

Situation

Customer has a valid entitlement with Micro Focus in order to mirror OES repositories into SUSE Manager, which might be already working for older releases of this operating system, OES. However, the new version, 2023, will not sync.
The sync log, located in /var/log/rhn/reposync will show something similar to this.

2022/11/22 11:29:06 +02:00 Command: ['/usr/bin/spacewalk-repo-sync', '--channel', 'oes2023-pool-x86_64', '--type', 'yum', '--non-interactive']
2022/11/22 11:29:06 +02:00 Sync of channel started.
2022/11/22 11:29:09 +02:00 RepoMDError: Cannot access repository.
Repository 'oes2023-pool-x86_64' is invalid.
[oes2023-pool-x86_64|http://1234567@nu.novell.com/repo/$RCE/OES2023-Pool/sle-15-x86_64/] Valid metadata not found at specified URL
History:
 - [|] Error trying to read from 'http://1234567@nu.novell.com/repo/$RCE/OES2023-Pool/sle-15-x86_64/'
 - Login failed. (http://1234567@nu.novell.com/repo/$RCE/OES2023-Pool/sle-15-x86_64/content): The requested URL returned error: 401

Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository 'oes2023-pool-x86_64' because of the above error.
Could not refresh the repositories because of errors.

As a result, these repositories cannot be used in SUSE Manager.

Resolution

A mass-PTF was made available in order to address this issue. It can be found under this url: https://ptf.suse.com/f2cf38b50ed714a8409693060195b235/susemanager-4.3/25430/x86_64/20230111
The PTF should be installed on top of the latest maintenance updates of SUSE Manager 4.3 (which is the minor version 4.3.3).

Cause

The url should include a string '1234567:<secret>'. The '<secret>' part was missing, causing this error. The code in the PTF corrects this issue.

Status

Reported to Engineering

Additional Information

Further information regarding best practices when installing PTFs can be found in the following TID: Best practice for applying Program Temporary Fixes (PTFs)
The error will be corrected in the code for next releases, probably in 4.3.4.
The same issue could exist in version 4.2. Should that be the case and the error not be corrected yet, a PTF could be requested to Support.

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.