One more thing to note, the architecture for me is different, meaning I still have 32 and 64 bit but with your script, the i386, i586,i686, ia32 did not work..
I launched to spacecmd, and ran command softwarechannel_details my-rhel5-32bit-channel The architecture for 32 bit os was listed as IA-32.. Defining IA-32 worked - just fyi.. Again thanks for the script.. Regards ilya -----Original Message----- From: [email protected] [mailto:[email protected]] On Behalf Of Paul Robert Marino Sent: Wednesday, May 02, 2012 4:27 PM To: [email protected] Subject: Re: [Spacewalk-list] Activation key and "Spacewalk Default" Thanks for the feed back I wrote the script to handle more than just RHEL so it varies from distro to distro Arch is fairly consistent 32 bit is almost always = i386 64 bit is almost always = x86_64 there are other Archs like ppc (Power PC Mac) and s390 (IBM Mainframe) but i386 or x86_64 are the ones most people use. OS changes by distro RedHat = redhat-release-server Sientific Linux = sl-release Release changes by distro and version RHEL 6.x = 6Server RHEL 5.x = 5Server Scientific Linux 6.2 = 6.2 Im honestly not sure what the settings for RHEL 4 should be since i don't ahve any RHEL 4 boxes running in production any more but two have 2 options to figure it out option 1 if you have a box currently registered to redhat network you can get it from the /etc/sysconfig/rhn/systemid file here is an example from RHEL 6 " <member> <name>description</name> <value><string>Initial Registration Parameters: OS: redhat-release-server Release: 6Server CPU Arch: x86_64</string></value> </member> " The second option is you can get it from the spacewalk error logs the error message should appear in /var/log/rhn/rhn_web_api.log and tell you what it tried to register as On Wed, May 2, 2012 at 2:57 PM, Musayev, Ilya <[email protected]> wrote: > 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: [email protected] > [mailto:[email protected]] On Behalf Of Paul Robert > Marino > Sent: Tuesday, May 01, 2012 8:08 PM > To: [email protected] > 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 <[email protected]> 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 >> [email protected] >> https://www.redhat.com/mailman/listinfo/spacewalk-list > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list > > > > _______________________________________________ > Spacewalk-list mailing list > [email protected] > https://www.redhat.com/mailman/listinfo/spacewalk-list _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list _______________________________________________ Spacewalk-list mailing list [email protected] https://www.redhat.com/mailman/listinfo/spacewalk-list
