You could try uploading all your Satellite certificates etc into
Spacewalk as config files, deploying them to all your clients, then run
a remote command to edit the /etc/sysconfig/rhn/up2date file (and any
others).
That's close to my plan for our Satellite upgrade as we've lost the
original
Spacewalk will be the upstream for the Satellite 5.x product.
Foreman/Katello will be the upstream for the Satellite 6 family.
Both projects will run separately (no code merge), and you'd have to
anticipate Red Hat putting much less effort into Spacewalk once
Satellite 6 is released. I would
Have a look at:
https://fedorahosted.org/spacewalk/wiki/JabberAndOSAD
for some pretty good help on trying to keep OSAD connected. I'm having
trouble on my Satellite estate at the moment, despite imlpementing the
advice here. Under investigation at the moment.
Cheers
D
: [Spacewalk-list] connection refused with rhnreg_ks
Innes, Duncan wrote:
% I was getting the same situation over the weekend, but was
running % rhn_register as I hadn't got as far as creating
activation keys.
%
% I'm running Spacewalk 2.1 on Fedora 19 (each fully updated)
and created
I was getting the same situation over the weekend, but was running
rhn_register as I hadn't got as far as creating activation keys.
I'm running Spacewalk 2.1 on Fedora 19 (each fully updated) and created
an empty channel for F19 x86_64. Does this match your installation at
all?
The error was
Brendan,
I follow the following advice:
https://fedorahosted.org/spacewalk/wiki/JabberAndOSAD
even though it seems to be using a sledgehammer to crack a nut. Would
be nicer if OSAD were a little more reliable, or it's status was more
easily queriable (word?) from the client side.
Hi folks,
Is there a way of checking the connectivity status of osad from the
client side? I know I can query the Satellite to show the OSA Status of
each client, but am wondering about being able to do this on the client
side so that (for example) a Nagios check can be built for all RHEL
