Fixing SUSE 15 Repository and Registration Issues

by

Introduction

If you’re managing SUSE 15 machines, you might encounter a frustrating issue where repositories fail to refresh, and SUSEConnect shows all products as “Not Registered.” This problem can prevent package installations and disrupt your operations. While SUSE’s public documentation provides troubleshooting steps, they may not always resolve the issue. In this guide, we’ll walk you through the symptoms, troubleshooting steps, and a proven mitigation strategy to fix SUSE 15 repository and registration issues.

Symptoms of the Issue

You may notice the following symptoms on your SUSE 15 machine:

  • Zypper refresh fails: The system cannot find any repositories.
  • SUSEConnect status: Running SUSEConnect --status shows all products as “Not Registered.”

These symptoms might resemble common registration or connectivity issues, but the usual troubleshooting steps won’t resolve this particular problem.

Troubleshooting Steps

1. Verify Basic Connectivity and Registration

Start with the basic troubleshooting steps outlined in SUSE’s documentation:

  • Run:
SUSEConnect --cleanup  
registercloudguest --force-new  
SUSEConnect --status
  • Check connectivity using the sc-repocheck.py script:
python3 <(curl --location --silent https://raw.githubusercontent.com/rfparedes/susecloud-repocheck/main/sc-repocheck.py)

If these steps fail, you’re likely facing a known issue with outdated registration packages.

Mitigation Strategy

To resolve this issue, you’ll need to manually update the registration packages on the problematic machine. Here’s how:

Step 1: Extract Registration Packages from a Working Machine

  • On a working SUSE machine with the same Service Pack (SP), run the following commands:
zypper --pkg-cache-dir /tmp/ts/packages/ download cloud-regionsrv-client cloud-regionsrv-client-plugin-azure regionServiceClientConfigAzure python3-azuremetadata SUSEConnect python3-cssselect python3-toml python3-lxml python3-M2Crypto python3-zypp-plugin  
mkdir /tmp/ts/rpms  
find /tmp/ts/packages/ -type f -name "*.rpm" -exec cp {} /tmp/ts/rpms/ \;  
cd /tmp/ts/  
tar -czvf suse-sp4-public-registration.tgz rpms
  • After completion, remove the temporary folder: 
rm -rf /tmp/ts

Step 2: Copy and Install Packages on the Problematic Machine

  • Transfer the suse-sp4-public-registration.tgz file to the problematic machine.
  • Extract the file:
tar xvfz suse-sp4-public-registration.tgz  
cd rpms
  • Install the packages: 
zypper --no-refresh --no-remote install *.rpm
  • When prompted, choose option 2 and select Yes.
  • Run the following commands to clean up and re-register the system:
SUSEConnect --cleanup  
registercloudguest --force-new  
SUSEConnect --status

Step 3: Refresh Repositories

Finally, refresh the repositories to ensure everything is working:

zypper refresh

Additional Notes

  • Take Precautions: Always create an OS disk snapshot before making changes.
  • Keep Packages Updated: Outdated packages are often the root cause of these issues. Encourage customers to regularly update their systems.
  • End-of-Life Products: Most cases involve SUSE 15 SP2, SP3, and SP4, which have reached their end of life. Customers should verify if they have Long Term Service Pack Support (LTSS).

For more details on product lifecycle, refer to the SUSE Product Support Lifecycle.

Conclusion

SUSE 15 repository and registration issues can be challenging, especially when standard troubleshooting steps fail. By manually updating the registration packages, you can resolve this issue and restore your system’s ability to install packages.

If you found this guide helpful, share it with your colleagues or bookmark it for future reference. For more tips and troubleshooting guides, subscribe to our newsletter or leave a comment below!

Leave a Comment