[katello] errata for Scientific Linux & Cent OS

Hey All,

I'm starting to look at using Katello in our organisation as a method for
patching & reporting. We are concerned mainly with the reporting side at
this point in time, so errata information is important.

I understand that CentOS only post their errata data to a mailing list, and
don't include it in the repodata - so this one requires a bit of extra
work…

What I'm not sure on is why the Scientific Linux mirroring isn't pulling in
the errata data as well. In the Scientific Linux repos/repotdata there is a
file which contains this information.

http://mirror.aarnet.edu.au/pub/scientific/6.6/x86_64/os/repodata/updateinfo.xml

So given this, my questions are;
What file does katello/pulp look for when pulling in errata data?
Can I manually pull in this file via pulp-admin? (pulp-admin rpm repo
uploads erratum (?) )

Any assistance/direction would be great, as errata data provides so much
more to just mirroring repos!

Thanks
David

This data is coming from the repomod.xml file in the source repository.
You could add the errata via pulp, but I would be concerned that the
next sync might overwrite the medatata. I will send this along to the
pulp folks to see what they say.

– bk

··· On 12/09/2014 09:53 PM, David LeVene wrote: > Hey All, > > I'm starting to look at using Katello in our organisation as a method > for patching & reporting. We are concerned mainly with the reporting > side at this point in time, so errata information is important. > > I understand that CentOS only post their errata data to a mailing list, > and don't include it in the repodata - so this one requires a bit of > extra work.. > > What I'm not sure on is why the Scientific Linux mirroring isn't pulling > in the errata data as well. In the Scientific Linux repos/repotdata > there is a file which contains this information. > > http://mirror.aarnet.edu.au/pub/scientific/6.6/x86_64/os/repodata/updateinfo.xml > > So given this, my questions are; > What file does katello/pulp look for when pulling in errata data? > Can I manually pull in this file via pulp-admin? (pulp-admin rpm repo > uploads erratum (?) ) >

Thanks for both of the replies… i've raised a couple of bug/feature reqs
and they are located here,

Scientific Linux Errata Data does not get imported -
https://bugzilla.redhat.com/show_bug.cgi?id=1172887

Ability to import errata data from an external source. -
http://projects.theforeman.org/issues/8656

Cheers
David

>
> Putting this here in case anyone is interested. The script is not that
> great and I created it while stumbling around with the PERL code, but it's
> working for me so it might be able to help others.
>

For the issue with scientific linux, I would recommend filing a pulp
bug: https://bugzilla.redhat.com/enter_bug.cgi?product=Pulp

as it sounds like they are not syncing the errata properly (as its
possible the errata is formatted differently than RHEL).

For the ability to 'import' errata in cases where an updateinfo.xml is
not provided, I'd recommend filing an RFE in katello
http://projects.theforeman.org/projects/katello/issues/new

-Justin

··· On 12/10/2014 08:49 AM, Bryan Kearney wrote: > > > On 12/09/2014 09:53 PM, David LeVene wrote: >> Hey All, >> >> I'm starting to look at using Katello in our organisation as a method >> for patching & reporting. We are concerned mainly with the reporting >> side at this point in time, so errata information is important. >> >> I understand that CentOS only post their errata data to a mailing list, >> and don't include it in the repodata - so this one requires a bit of >> extra work.. >> >> What I'm not sure on is why the Scientific Linux mirroring isn't pulling >> in the errata data as well. In the Scientific Linux repos/repotdata >> there is a file which contains this information. >> >> http://mirror.aarnet.edu.au/pub/scientific/6.6/x86_64/os/repodata/updateinfo.xml >> >> >> So given this, my questions are; >> What file does katello/pulp look for when pulling in errata data? >> Can I manually pull in this file via pulp-admin? (pulp-admin rpm repo >> uploads erratum (?) ) >> > > This data is coming from the repomod.xml file in the source > repository. You could add the errata via pulp, but I would be > concerned that the next sync might overwrite the medatata. I will send > this along to the pulp folks to see what they say. > > -- bk >

Were you able to confirm that the "next sync" overwrite meta data? I found
an interesting post
here http://blog.vmfarms.com/2013/12/inject-little-security-in-to-your.html
which could prove useful in syncing centos errata's into katello.

··· On Thursday, 11 December 2014 13:45:51 UTC+11, David LeVene wrote: > > Thanks for both of the replies... i've raised a couple of bug/feature reqs > and they are located here, > > Scientific Linux Errata Data does not get imported - > https://bugzilla.redhat.com/show_bug.cgi?id=1172887 > > Ability to import errata data from an external source. - > http://projects.theforeman.org/issues/8656 > > > Cheers > David >

Hi Andrew,

No, this has taken a back seat in our project world as we mainly use
Scientific Linux which has had a patch released for it to support bz2. I
would expect the behavior of the next sync to overwrite the metadata - as
you are telling pulp to use a remote repo as the master(just an educated
guess).

Cheers
David

··· On Friday, 27 March 2015 14:57:29 UTC+10:30, Andrew Lau wrote: > > Were you able to confirm that the "next sync" overwrite meta data? I found > an interesting post here > http://blog.vmfarms.com/2013/12/inject-little-security-in-to-your.html > > which could prove useful in syncing centos errata's into katello. > > On Thursday, 11 December 2014 13:45:51 UTC+11, David LeVene wrote: >> >> Thanks for both of the replies... i've raised a couple of bug/feature >> reqs and they are located here, >> >> Scientific Linux Errata Data does not get imported - >> https://bugzilla.redhat.com/show_bug.cgi?id=1172887 >> >> Ability to import errata data from an external source. - >> http://projects.theforeman.org/issues/8656 >> >> >> Cheers >> David >> >

Interesting, I sync'd the centos updates repo on a different server and
tried injecting the errata updates however no luck so far.

This may prove to be a potential compromise to importing erratas into
katello for centos…

··· On 30 March 2015 at 10:58, David LeVene wrote:

Hi Andrew,

No, this has taken a back seat in our project world as we mainly use
Scientific Linux which has had a patch released for it to support bz2. I
would expect the behavior of the next sync to overwrite the metadata - as
you are telling pulp to use a remote repo as the master(just an educated
guess).

Cheers
David

On Friday, 27 March 2015 14:57:29 UTC+10:30, Andrew Lau wrote:

Were you able to confirm that the “next sync” overwrite meta data? I
found an interesting post here http://blog.vmfarms.com/
2013/12/inject-little-security-in-to-your.html
http://www.google.com/url?q=http%3A%2F%2Fblog.vmfarms.com%2F2013%2F12%2Finject-little-security-in-to-your.html&sa=D&sntz=1&usg=AFQjCNErTs4GuxGm0m6j_D4yJDBctan6JQ
which could prove useful in syncing centos errata’s into katello.

On Thursday, 11 December 2014 13:45:51 UTC+11, David LeVene wrote:

Thanks for both of the replies… i’ve raised a couple of bug/feature
reqs and they are located here,

Scientific Linux Errata Data does not get imported -
https://bugzilla.redhat.com/show_bug.cgi?id=1172887

Ability to import errata data from an external source. -
Feature #8656: Ability to import errata data from an external source. - Katello - Foreman
http://www.google.com/url?q=http%3A%2F%2Fprojects.theforeman.org%2Fissues%2F8656&sa=D&sntz=1&usg=AFQjCNFE-xggrGq9Bx2xDHvfPyMwXkAZIQ

Cheers
David


You received this message because you are subscribed to a topic in the
Google Groups “Foreman users” group.
To unsubscribe from this topic, visit
https://groups.google.com/d/topic/foreman-users/V8b6la3CMpI/unsubscribe.
To unsubscribe from this group and all its topics, send an email to
foreman-users+unsubscribe@googlegroups.com.
To post to this group, send email to foreman-users@googlegroups.com.
Visit this group at http://groups.google.com/group/foreman-users.
For more options, visit https://groups.google.com/d/optout.