[Spacewalk-list] Migrating from 2.7 to 2.9

[William Hongach]

Hello,

I can confirm that my 2.9 clients are checking in with the 2.8 server successfully.  I did notice a change in the frequency of rhn_check, however.  It now uses rhnsd.timer which may account for the change in behavior that you're seeing.

-----Original Message-----
From: spacewalk-list-bounces at redhat.com <spacewalk-list-bounces at redhat.com> On Behalf Of Michael Mraka
Sent: Tuesday, July 2, 2019 8:29 AM
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] Migrating from 2.7 to 2.9

Paul Greene:
> I probably jumped the gun on the slow response rate of the remote 
> tasks I'd scheduled - they eventually did kick in
> 
> But, if anyone has some input on whether or not there's likely to be 
> an issue because I didn't update the clients, I'd eagerly appreciate 
> some feedback.
...
> > Maybe I'm overthinking it, but I'm wondering if not updating any of 
> > the client packages to 2.9 is going to cause any issues that aren't 
> > initially apparent. I tried to push out some remote commands to a 
> > group of 7 systems, and I usually start seeing some successful 
> > and/or failed actions within maybe 15 minutes or so, but it's been 
> > about an hour and a half now and there hasn't been any movement yet on the remote tasks.
> >
> > Can anyone think of any potential issues I might be running in to 
> > taking this route?

Generally Spacewalk server and clients of different version are compatible.
If not clients would complain in the log (during each rhn_check).
AFAIK there were no API change since 2.7.

Regards,

--
Michael Mráka
System Management Engineering, Red Hat

_______________________________________________
Spacewalk-list mailing list
Spacewalk-list at redhat.com
https://www.redhat.com/mailman/listinfo/spacewalk-list