Configuring SMT 1.0 servers to use self-hosted repositories
This document (7002607) is provided subject to the disclaimer at the end of this document.
Environment
Novell Subscription Management Tool
Novell SUSE Linux Enterprise Server 10 Service Pack 2
Novell SUSE Linux Enterprise Server 10 Service Pack 2
Situation
When Subscription Management Tool (SMT) is installed on a SUSE
Linux Enterprise server, it registers itself with the update
service at https://nu.novell.com and
subscribes to the appropriate update repositories (catalogs)
provided at that location. For the time being the catalogs needed
are SLES10-SP2-Updates andSLE10-SP2-SMT-Updates.
Since the SMT utilities looks at the url parameter in /etc/suseRegister.conf when synchronizing available catalogs, updates and registrations, this parameter must remain unchanged and thus the SMT server stays registered with with nu.novell.com.
Unfortunately this leads to the inefficient behavior that the SMT server will download the patches needed during update of itself - even though they may already be present in mirrored catalogs on the server itself.
Since the SMT utilities looks at the url parameter in /etc/suseRegister.conf when synchronizing available catalogs, updates and registrations, this parameter must remain unchanged and thus the SMT server stays registered with with nu.novell.com.
Unfortunately this leads to the inefficient behavior that the SMT server will download the patches needed during update of itself - even though they may already be present in mirrored catalogs on the server itself.
Resolution
It is possible to work around this situation by doing the following
:
So if there is a need to register the SMT server against nu.novell.com again after implementing this workaround, then do it via the command-line utility /usr/bin/suse_register like this :
- Make sure the SLES10-SP2-Updates andSLE10-SP2-SMT-Updates catalogs are mirrored for the architecture of the server.
- Delete the https://nu.novell.com
service with the command
rug service-delete https://nu.novell.com
This also deletes the catalogs. - Add the SLES10-SP2-Updates and SLE10-SP2-SMT-Updates repositories on the server itself as YUM services :
rug service-add -t yum http://<url-of-your-smt-server>/repo/\$RCE/SLES10-SP2-Updates/<target>/ SLES10-SP2-Updates
e.g.rug service-add -t yum http://my-smt.mycompany.com/repo/\$RCE/SLES10-SP2-Updates/sles-10-x86_64/ SLES10-SP2-Updates
andrug service-add -t yum http://<url-of-your-smt-server>/repo/\$RCE/SLE10-SP2-SMT-Updates/<target>/ SLE10-SP2-SMT-Updates
e.g.rug service-add -t yum http://my-smt.mycompany.com/repo/\$RCE/SLE10-SP2-SMT-Updates/sles-10-x86_64/ SLE10-SP2-SMT-Updates
- Verify that the services both show up with
rug service-list
- Subscribe to the SLES10-SP2-Updates and SLE10-SP2-SMT-Updates
catalogs :
rug subscribe SLES10-SP2-Updates
rug subscribe SLE10-SP2-SMT-Updates
So if there is a need to register the SMT server against nu.novell.com again after implementing this workaround, then do it via the command-line utility /usr/bin/suse_register like this :
suse_register -a regcode-sles=YourActivationCode -a email=YourEmailAddress
Disclaimer
This Support Knowledgebase provides a valuable tool for NetIQ/Novell/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:7002607
- Creation Date:10-FEB-09
- Modified Date:27-APR-12
- SUSESubscription Management ToolSUSE Linux Enterprise Server
Did this document solve your problem? Provide Feedback
