Repositories are not registered after running suse_register
This document (7003779) is provided subject to the disclaimer at the end of this document.
Environment
Subscription Management Tool
SUSE Linux Enterprise Desktop 11
SUSE Linux Enterprise Server 11
SUSE Linux Enterprise Desktop 11
SUSE Linux Enterprise Server 11
Situation
After a successful execution of /usr/bin/suse_register against a Subscription Management Tool (SMT), server the update repositories are not visible.
The update service is listed with a type of NONE and no repositories have been added as can be seen from this dialog :
host1:~ # suse_register --restore-repos
host1:~ # zypper ls
# | Alias | Name | Enabled | Refresh | Type
--+-------------------------+-------------------------+---------+---------+------
1 | SMT-http_smt11d_nts_com | SMT-http_smt11d_nts_com | Yes | No | NONE
2 | CD1 | CD1 | Yes | Yes | yast2
host1:~ # zypper lr
# | Alias | Name | Enabled | Refresh
--+-------+------+---------+--------
1 | CD1 | CD1 | Yes | Yes
host1:~ #
Rebooting the host does also not resolve the problem.
The update service is listed with a type of NONE and no repositories have been added as can be seen from this dialog :
host1:~ # suse_register --restore-repos
host1:~ # zypper ls
# | Alias | Name | Enabled | Refresh | Type
--+-------------------------+-------------------------+---------+---------+------
1 | SMT-http_smt11d_nts_com | SMT-http_smt11d_nts_com | Yes | No | NONE
2 | CD1 | CD1 | Yes | Yes | yast2
host1:~ # zypper lr
# | Alias | Name | Enabled | Refresh
--+-------+------+---------+--------
1 | CD1 | CD1 | Yes | Yes
host1:~ #
Rebooting the host does also not resolve the problem.
Resolution
In SUSE Linux Enterprise 11 the zypper tool is used for repository and update management and it works different than the rug tool in previous versions.
For technical reasons suse_register is currently not able to issue a refresh of the repositories after the registration of the service, so it needs to be done manually with the command
host1:~ # zypper ref -s
Refreshing service 'SMT-http_smt11d_nts_com'.
Adding repository 'SLES11-Updates' [done]
All services have been refreshed.
Repository 'CD1' is up to date.
Retrieving repository 'SLES11-Updates' metadata [done]
Building repository 'SLES11-Updates' cache [done]
All repositories have been refreshed.
host1:~ # zypper ls
# | Alias | Name | Enabled | Refresh | Type
--+-------------------------+-------------------------+---------+---------+------
1 | SMT-http_smt11d_nts_com | SMT-http_smt11d_nts_com | Yes | No | ris
2 | CD1 | CD1 | Yes | Yes | yast2
host1:~ # zypper lr
# | Alias | Name | Enabled | Refresh
--+----------------------------------------+----------------+---------+--------
1 | CD1 | CD1 | Yes | Yes
2 | SMT-http_smt11d_nts_com:SLES11-Updates | SLES11-Updates | Yes | Yes
The real fix to this issue is a new version of the suse_register executable that needs to be on the installation medium.
This is available in SLED/SLES 11 Support Pack one where the problem does not exist any more.
For technical reasons suse_register is currently not able to issue a refresh of the repositories after the registration of the service, so it needs to be done manually with the command
# zypper refresh --servicesor simply
# zypper ref -sAfter this the service type will change from NONE to ris (Repository Index Service) and the available repositories will show up in the list. An example of commands and output is shown here :
host1:~ # zypper ref -s
Refreshing service 'SMT-http_smt11d_nts_com'.
Adding repository 'SLES11-Updates' [done]
All services have been refreshed.
Repository 'CD1' is up to date.
Retrieving repository 'SLES11-Updates' metadata [done]
Building repository 'SLES11-Updates' cache [done]
All repositories have been refreshed.
host1:~ # zypper ls
# | Alias | Name | Enabled | Refresh | Type
--+-------------------------+-------------------------+---------+---------+------
1 | SMT-http_smt11d_nts_com | SMT-http_smt11d_nts_com | Yes | No | ris
2 | CD1 | CD1 | Yes | Yes | yast2
host1:~ # zypper lr
# | Alias | Name | Enabled | Refresh
--+----------------------------------------+----------------+---------+--------
1 | CD1 | CD1 | Yes | Yes
2 | SMT-http_smt11d_nts_com:SLES11-Updates | SLES11-Updates | Yes | Yes
The real fix to this issue is a new version of the suse_register executable that needs to be on the installation medium.
This is available in SLED/SLES 11 Support Pack one where the problem does not exist any more.
Additional Information
Fixed in SLE11 SP1.
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.
- Document ID:7003779
- Creation Date: 07-Jul-2009
- Modified Date:28-Sep-2022
-
- Subscription Management Tool
- SUSE Linux Enterprise Desktop
- SUSE Linux Enterprise Server
For questions or concerns with the SUSE Knowledgebase please contact: tidfeedback[at]suse.com
