PDA

View Full Version : Registering SLE 11 SP2 systems with SUSE Manager?



allenb_1121
27-Mar-2012, 15:00
When I try to use my bootstrap script to register SLE 11 SP2 systems to SUSE Manager, I get the error I have pasted to the bottom of this message.

Indeed, the path: /pub/repositories/sle/11/2/bootstrap does not exist. /pub/repositories/sle/11/1/bootstrap does exist.
The SP1 client seems to work fine, but my questions are this:
1. Is there a channel for SP2 that I'm not seeing for some reason?
2. If not, what is the preferred fix? I know I could use a symlink, copy the directory, or us an apache alias or rewrite rule to fix this, but I don't want to put something in that will cause a problem when an update comes down that tries to create that directory.
Has anyone else run into this problem, and how did you correct it?

Thanks.
Allen B.

CHECKING THE REGISTRATION STACK
-------------------------------------------------
* check for necessary packages being installed...
* client codebase is sle-11-sp2
package spacewalk-check is not installed
package spacewalk-client-setup is not installed
package spacewalk-client-tools is not installed
package zypp-plugin-spacewalk is not installed
* going to install missing packages...
adding client software repository at http://servername.ua.edu/pub/repositories/sle/11/2/bootstrap
Retrieving repository 'susemanager-client-setup' metadata [error]
Repository 'susemanager-client-setup' is invalid.
[|] Valid metadata not found at specified URL(s)
Please check if the URIs defined for this repository are pointing to a valid repository.
Skipping repository 'susemanager-client-setup' because of the above error.
Could not refresh the repositories because of errors.
Retrieving repository 'susemanager-client-setup' metadata [error]
Repository 'susemanager-client-setup' is invalid.
[|] Valid metadata not found at specified URL(s)
Please check if the URIs defined for this repository are pointing to a valid repository.
Warning: Disabling repository 'susemanager-client-setup' because of the above error.
Loading repository data...
Reading installed packages...
'spacewalk-check' not found in package names. Trying capabilities.
No provider of 'spacewalk-check' found.
'spacewalk-client-setup' not found in package names. Trying capabilities.
No provider of 'spacewalk-client-setup' found.
'spacewalk-client-tools' not found in package names. Trying capabilities.
No provider of 'spacewalk-client-tools' found.
'zypp-plugin-spacewalk' not found in package names. Trying capabilities.
No provider of 'zypp-plugin-spacewalk' found.
ERROR: Failed to install all missing packages.

allenb_1121
27-Mar-2012, 15:26
I forgot to mention that I got around the issue with a symlink, by doing this:
mkdir /srv/www/htdocs/pub/repositories/sle/11/2
ln -s /srv/www/htdocs/pub/repositories/susemanager-client-setup /srv/www/htdocs/pub/repositories/sle/11/2/bootstrap

I am just asking if that was the best solution, or if there is a better way? Is something broken with my setup that it didn't create that automatically?

Allen B.

malcolmlewis
05-Apr-2012, 16:16
I forgot to mention that I got around the issue with a symlink, by doing
this:
mkdir /srv/www/htdocs/pub/repositories/sle/11/2
ln -s /srv/www/htdocs/pub/repositories/susemanager-client-setup
/srv/www/htdocs/pub/repositories/sle/11/2/bootstrap

I am just asking if that was the best solution, or if there is a better
way? Is something broken with my setup that it didn't create that
automatically?

Allen B.



Hi
Do you have SLED11-SP2-Core and SLED11-SP1-Updates available as that's
where the spacewalk files exist.

--
Cheers Malcolm °¿° (Linux Counter #276890)
SUSE Linux Enterprise Desktop 11 (x86_64) Kernel 3.0.13-0.27-default
up 21:21, 3 users, load average: 0.05, 0.03, 0.05
CPU Intel i5 CPU M520@2.40GHz | Intel Arrandale GPU

allenb_1121
06-Apr-2012, 16:24
Yes, those channels are available, and everything works just fine. It is just that the provided bootstrap script (that I edited with my activation key, etc...) is looking for servername/pub/repositories/sle/11/2 as an install source, and that does not exist on my server - this is just for initial activation against the server. I worked around that just fine by creating a symlink of /pub/repositories/sle/11/1 there

Allen B.