Automation to add Red Hat errata from Red Hat channel to Custom channel

Latest response

Great Group. I get a lot from your discussions. 

I have what I hope is a good question for the Group. 

Has anyone created automation to Add all the errata from a Red Hat channel to a Custom channel that is a clone of the Red Hat channel?

I have a script in place to synchronize packages from Red Hat Network to my Satellite and would like to create another script that would, once a month, add all the errata from that Red Hat Channel to my Custom channel that is it's clone.

Is anyone else doing something like this? 

~thanks

AT
Log in to join the conversation

Responses

PM Red Hat Guru 3594 points
8 May 2013 8:43 AM

Hi Matt,

I haven't written a script but I see that it is very much doable with the help of RHN Satellite API's. You can use the API which lists the errata's applicable to the cloned channel and then use clone errata api to clone those errata's into the specific clone channel.

Paresh

David Powles's picture Red Hat 25369 points
8 May 2013 11:15 AM

Matt,

Unfortunately I can't help you out with a script, but if you haven't already seen it there's an API solutions discussion here in the group, so if you do come up with a solution along those lines, we'd love to hear about it there.

 

AT Community Member 38 points
8 May 2013 12:51 PM

Thanks for your pointers Paresh and David. I don't have much experience with the API, but this will be the perfect opportunity to get familiar. When I have a working script, I will share it in the API discussion.

mm Pro 520 points
14 May 2013 3:15 PM

There's a script in the community called spacewalk-manage-channel-lifecycle.  I've been using it and just published a bug fix to the spacewalk user mailing list.  It uses the APIs in a python script to create channels, promote content, etc.  You can do rollbacks but you need to create an archive first, otherwise you wind up with an empty channel.  There's no real documentation, but the script isn't that tough to follow.  

Currently, it doesn't work with an external repo as a child channel, i.e. if you publish EPEL as a child of RHEL 5.  I haven't done a lot of troubleshooting on that yet.  Doesn't seem to be a lot of community interest in this for some reason.

Here's the Fedora pastebin link http://paste.fedoraproject.org/12067/ b/c it's kinda long.  

(It'll disappear after 1 month, so if there's a better way to attach things to discussions please let me know.) 

Or, you can try clone-by-date with a config file like discussed in another thread (https://access.redhat.com/discussion/erratapackage-handling-satellite-server-cloned-channels#comment-88345) and add some wrapper automation around that process.

R. Hinton's picture Guru 6827 points
19 March 2014 1:11 AM

That last link seems to have moved here

Close

Welcome! Check out the Getting Started with Red Hat page for quick tours and guides for common tasks.