its now in the web interface its under Channels->Distribution Channel Mapping
On Mon, Jan 14, 2013 at 3:06 PM, Musayev, Ilya <[email protected]> wrote: > Hi Paul, > > Spacewalk 1.8 deprecated the api call distchannel.setDefaultMap - how we do > this with 1.8 - if you know? > > Thanks > ilya > > -----Original Message----- > From: [email protected] > [mailto:[email protected]] On Behalf Of Paul Robert Marino > Sent: Monday, November 19, 2012 11:23 AM > To: [email protected] > Subject: Re: [Spacewalk-list] Can't register RHEL5 host with 'spacewalk > default' key > > officially spacewalk 1.7 didn't have that capability however I did write a > script to make it work note it does work correctly in 1.8 without my script. > one of the major differences between what my script does and what the new > version does is when i wrote my script the table wasn't organization aware so > all mappings were global that has changes in 1.8 which is a good thing. > there were also some other odd bugs I ran into while rebuilding hosts see the > ticket here > https://bugzilla.redhat.com/show_bug.cgi?id=809936 > > here is the URL to the script on github > https://github.com/prmarino1/Extravehicular-Activity-Admin/blob/master/channel-managment/eva-dist-channel-map.pl > > all things said and done I highly suggest you move to version 1.8 even though > its new the number of thing that were known to be broken in 1.7 that were > fixed in 1.8 makes it worth it. > > > On Mon, Nov 19, 2012 at 11:08 AM, Jan Pazdziora <[email protected]> wrote: >> On Mon, Nov 19, 2012 at 03:57:43PM +0000, Snyder, Chris wrote: >>> I'm using Spacewalk 1.7 (1.8 is too new to try yet, going to let the bugs >>> shake out a bit first) and I want to be able to kickstart a RHEL 5 x86_64 >>> host and have it automatically registered to the appropriate base channel ( >>> and spacewalk client child channel) using the 'Spacewalk Default' key. >>> However, rhnreg_ks always fails to register my new host to ANY channels >>> when I try this. As far as I can tell I'm doing everything right, but >>> obviously I've missed something. I've been arguing with SW for over two >>> weeks trying to solve this and my head is going in circles now. Somebody >>> please save me! >>> >> >> Your staying on old version of Spacewalk prevents you from using new >> feature in Spacewalk 1.8 which would allow you to edit the mapping and >> see it working. >> >> -- >> Jan Pazdziora >> Principal Software Engineer, Satellite Engineering, Red Hat >> >> _______________________________________________ >> 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
