I will definitely try it tomorrow. Thanks for the script. Much appreciated.
On May 1, 2012, at 8:10 PM, "Paul Robert Marino" <[email protected]> wrote: > 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
