[Spacewalk-list] Activation key and "Spacewalk Default"

Musayev, Ilya imusayev at webmd.net
Wed May 2 18:57:03 UTC 2012


Hi Robert,

Would you  please make an example of  proper values for --os --release and --arch..

Reason I'm asking, I checked how the release and architecture is displayed under a sinlge system and it seems I could have multiple option.

As of now I have following, which one is correct? What would be a proper entry for RHAS 4 64 and 32 bit and RHEL server 5 32 bit? 


----------------------------------------------------------------------------
|         Channel Label        |    Operating System    | Release |  Arch  |
|------------------------------|------------------------|---------|--------|
|          rhel-x86_64-server-5|             rhel-server|        5|  x86_64|
|------------------------------|------------------------|---------|--------|
|          rhel-x86_64-server-5|                    rhel|        5|  x86_64|
|------------------------------|------------------------|---------|--------|
|          rhel-x86_64-server-5|          redhat-release|        5|  x86_64|
|------------------------------|------------------------|---------|--------|
----------------------------------------------------------------------------

It would help if you can show your --list to see how mapping is done or have another operation that can list what --arch --release and others can be set to.

Thanks
ilya

-----Original Message-----
From: spacewalk-list-bounces at redhat.com [mailto:spacewalk-list-bounces at redhat.com] On Behalf Of Paul Robert Marino
Sent: Tuesday, May 01, 2012 8:08 PM
To: spacewalk-list at redhat.com
Subject: Re: [Spacewalk-list] Activation key and "Spacewalk Default"

Its because the channels are not in the default dist map here is my tool for setting channels in the default dist map https://github.com/prmarino1/Extravehicular-Activity-Admin/blob/master/channel-managment/eva-dist-channel-map.pl

Note even though this script uses the published XML RPC APIs for spacewalk to do it this is not considered a supported operation at this time.
but its worked well for me and i hope it works for you.
by the way it has an embedded man file that can be extracted using the pod2text or pod2man tools.
let me know if it helps you



On Tue, May 1, 2012 at 6:32 PM, Musayev, Ilya <imusayev at webmd.net> wrote:
> I created several activation keys with "spacewalk default" as an 
> option for a channel. The "Tip" that is allows for systems to register 
> with default Redhat provided channel that corresponds to their installed version.
>
>
>
> My channels are named identically to what rhn has - i.e.
> rhel-x86_64-server-5. Why would the system that is being registered 
> does not pick up the channel? I only have 1 base channel that matches this system.
>
>
>
> I'm using rhel5.7 64 client and spacewalk 1.7
>
>
>
> Any help is appreciated.
>
>
>
> Thanks
>
> ilya
>
>
> _______________________________________________
> 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






More information about the Spacewalk-list mailing list