[Spacewalk-list] Errata synchronization issue with eva-direct-errata-sync.pl

[Pierre Casenove]

Hello,
Thanks Paul.
Could you please elaborate on your last chapter? I couldn't manage to find
a correct PKI cert to sync directly from Spacewalk.

Pierre


2014-02-27 6:33 GMT+01:00 Paul Robert Marino <prmarino1 at gmail.com>:

> I haven't run into this before. Im on vacation right now but ill look
> into it on my test spacewalk server when I get back into the office
> next week.
> In theory you shouldn't see erratas from channels you don't have
> access to on RHN's site so I'm not sure why you are. by the way it
> wouldnt be the first time when developing this script I found a bug in
> the upstream API's in fact there is an old one dating back to
> spacewalk 1.6 which is still a blocker for publicly releasing the code
> for my multi-basechannel sync feature. occasionally in the older
> errata API code you find some old very odd decisions which were made
> by some of the developers a long time ago which really date back to
> the old close source satellite days which I'm sure made sense at the
> time when they were written but have become problematic since then
> because of more complexity added by the code handling more distros and
> sub channels of those distros than satellite was originally designed
> to handle.
>
> In either case this would seem to be a bug in one of the upstream
> API's because they are allowing you to post two conflicting erratas
> and I'm a little unsure as to why they actually conflict when you try
> to push one out to the servers.
>
> In addition since Spacewalk 2.0 the only distro that still needs this
> script as far as I know is CentOS and I expect that to change soon.
> Even the Red Hat channels with subscription manager are now yum repos
> authenticated with PKI certs which spacewalk now supports. That said
> Ill see if I can find you a quick fix but I think going forward all of
> these errata sync scripts will become obsolete shortly so I don't
> intend to put too much effort into it any more other then bug fixes.
>
>
> On Wed, Feb 26, 2014 at 7:59 AM, Pierre Casenove <pcasenove at gmail.com>
> wrote:
> > Hello list,
> > I'm using eva-direct-errata-sync.pl to sync redhat errata to spacewalk.
> > I've just had a problem with the following erratas:
> > RHSA-2014:0015-1 : openssl security fix
> > RHEA-2014:0208-1 : RH Storage 2.1 enhancement errata
> >
> > The problem is that both of these erratas are linked to packages
> > openssl-1.0.1e-16.el6_5.4.
> > So the script created both errata.
> >
> > The problem is that when I wanted to schedule the errata 2014:0015-1
> using
> > the XMLRPC API, I received an error:
> > Fault returned from XML RPC Server, fault code 2600:
> > redstone.xmlrpc.XmlRpcFault: Invalid errata
> >
> > I had to delete errata 2014:0208 to be able to apply errata 2014:0015
> >
> > I think that eva-direct-errata-sync.pl has a bug as it should not create
> > errata 2014:0208 on my spacewalk server, because I don't have RH Storage
> > Server channels.
> > It seems that package openssl is in channels RH Storage Server AND RHEL
> > Server.
> > And eva script has created the errata because it found openssl package.
> >
> > Is it possible to specify to eva script to not sync channels RH Storage
> > Server ?
> >
> > I hope I'm clear on my issue.
> >
> > Thanks in advance for your help
> >
> > _______________________________________________
> > Spacewalk-list mailing list
> > Spacewalk-list at redhat.com
> > https://www.redhat.com/mailman/listinfo/spacewalk-list
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list
>
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://listman.redhat.com/archives/spacewalk-list/attachments/20140227/6a610ee3/attachment.htm>