[Spacewalk-list] Spacewalk-list Digest, Vol 68, Issue 11

[Paul Robert Marino]

Franky
You are wrong in spacewalk 2.x you can use the TLS certs generated
from subscription manager and just sync to standard yum repos with the
erratas on cdn.redhat.com it takes a little digging but you can find
the paths to the yum repos on access.redhat.com.
I've been doing it for a while on my test instance running 2.1. once I
put 2.1 in production after its release the only thing I will use my
script https://github.com/prmarino1/Extravehicular-Activity-Admin/blob/master/errata-tools/eva-direct-errata-sync.pl
for is CentOS and I don't see that lasting long because they are now
part of Red Hat and will probably start publishing erratas in their
yum repos too.




On Tue, Jan 14, 2014 at 4:00 AM, Franky Van Liedekerke
<liedekef at telenet.be> wrote:
> On 2014-01-14 03:09, Butcher, Nathan wrote:
>>
>> Am I just better off upgrading to Spacewalk 2.0?
>>
>> Also, I'm not sure how the ya-errata-import script works. I give it a
>> channel I have in spacewalk, and it can't find it, even though I know
>> it's there.
>> Maybe I'm unsure of what the --channel option is expecting? I've
>> tried "6" and "rhel6" and "rhel-x86_64-server-6"
>> I have my RHN and SPACEWALK credentials right (by sourcing the cfg file)
>
>
> The channel option requires the channel label (it's the only unique thing,
> other than the channel id).
> Examples can be found in the accompanying shell files.
>
> Upgrading to spacewalk 2.0 won't change anything to your subscription
> process with redhat.
>
>
> Franky
>
> _______________________________________________
> Spacewalk-list mailing list
> Spacewalk-list at redhat.com
> https://www.redhat.com/mailman/listinfo/spacewalk-list