Red Hat Bugzilla – Bug 183216
rhnpush should use header fields to determine when it's communicating with and older satellite
Last modified: 2013-02-26 19:49:47 EST
Description of problem: rhnpush needed a way to tell when it was communicating
with an older satellite when I added session-token support. Unfortunately, I
decided to use a try-catch around an XML-RPC call to tell when I was
communicating with an older satellite. This will cause a traceback on the
satellite if the --no-session-caching option isn't used. This is annoying.
rhnpush should look for the existence of a header field to determine what
version of satellite it's communicating with. It would then be able to use the
existence and possible the value of the field to determine how it should
communicate with the satellite it's pointed at.
This will require a server-side change that will add a field to the header of
the response generated by a ping request. It will also require a client-side
change where rhnpush will look for the new header field to figure out which set
of XMLRPC calls to use.
How is this any different than a server-capability that's delivered on the ping
Keeping this one on -triage for now...
It's not really, that I can see. I talked to pkilambi about it a few days ago
and this is what he's doing for another rhnpush bug. It seemed sane and would
fix a problem with another section of code that I wrote, so I filed a bug so I
could implement it.
Re-aligning against rhn420-triage.