[Spacewalk-list] [rhn-satellite-users] Client Configuration Guide: 2.2.4. Implementing Server Failover

[Aaron Prayther]

It never made sense to me how the client rhn_register would work, etc and being able to fail over by simply adding a satellite to the up2date file.

Because, duh.  You have to have satellite setup in a failover configuration as outlined in the satellite_failover.pdf

Which makes perfect sense. My problem is that I just don't want to use the external db.  The only defense I have is that the client configuration document that shows howto setup client failover could reference that fact.

Sorry for being dense,

Aaron Prayther

-----Original Message-----
From: rhn-satellite-users-bounces at redhat.com [mailto:rhn-satellite-users-bounces at redhat.com] On Behalf Of inode0
Sent: Wednesday, January 19, 2011 12:40 PM
To: rhn-satellite-users at redhat.com
Subject: Re: [rhn-satellite-users] Client Configuration Guide: 2.2.4. Implementing Server Failover

On Wed, Jan 19, 2011 at 10:51 AM, Aaron Prayther <aprayther at lce.com> wrote:
> Maybe enter a ticket at red hat.  Seems to me that we just got really
> close to confirming this is a red hat/satellite issue and not just me
> being silly.  I have a ticket in.  I'm thinking squeaky wheel.  If any
> of you red hat folks out there have another suggestion/better ways on
> how to pursue this.  I'll do whatever you need... to a certain extent =)

A bit more testing and I see it does still work on RHEL4 systems,
fails on RHEL5 systems, haven't tested RHEL6 yet.

John

--
rhn-satellite-users mailing list
rhn-satellite-users at redhat.com
https://www.redhat.com/mailman/listinfo/rhn-satellite-users