I thought i'd work for a new kickstart machine...for example if I put these packages they won't be installed, because first - you need to register your machine. I then you need to add packages into your kickstart. rhn-client-tools rhn-check rhn-setup rhnsd m2crypto yum-rhn-plugin rhncfg-actions rhn-virtualization-host
On Thu, Apr 7, 2016 at 3:59 PM, Avi Miller <[email protected]> wrote: > Hi, > > It works fine for me. :) YMMV. > > 1. Deploy the GPG keys for your target channels (via Kickstart or > Configuration Channel or some other method) > 2. Ensure the correct software channels are enabled for the activation key > 3. List the packages you want installed by that key > > The kicker is usually step 1: making sure your target systems have the > appropriate GPG key for the packages you want the activation key to > install. It would be super peachy keen if you could associate GPG keys with > activation keys so that it's more obvious. > > Note that step 2 can be tricky too, because the activation key will > override the kickstart channels. So it's not cumulative, it's a replacement. > > Cheers, > Avi > > On 8 Apr 2016, at 8:42 AM, Lachlan Musicman <[email protected]> wrote: > > Konstantin, > > I disagree with Avi in that "it works". I have also not known it to work > on Kickstarted machines. I found I had to add the packages to the software > list under profiles. > > I am sure that is how it's meant to work - it would appear to be a good > thing and an obvious functionality. But I've never known it to work either. > My suspicion is on the cobbler/spacewalk snippets, but it's hard to pin > down. > > I also found that the files weren't distributed on Kickstart without > shoe-horning them in with a post install script. > > Let me know if you need the script to see it working. > > Cheers > L. > > ------ > The most dangerous phrase in the language is, "We've always done it this > way." > > - Grace Hopper > > On 8 April 2016 at 07:41, Avi Miller <[email protected]> wrote: > >> It works if the packages are in a channel that is activated by the same >> key. It also requires any GPG keys required by those packages to already be >> installed on the target system. >> >> On the plus side, it works regardless of whether the system was >> kickstarted by Spacewalk or not. Assuming you have the keys in place, any >> system registered with that key will attempt to install the packages listed. >> >> > On 8 Apr 2016, at 6:23 AM, Konstantin Raskoshnyi <[email protected]> >> wrote: >> > >> > I found a great function, if you go to Systems->Activation >> keys->%KEY%->Packages >> > >> > Seems like they should be installed on every system kickstarted with >> this key. >> > >> > But it doesn't work. There're no logs too. >> > >> > I feel like this works only the system added to the spacewalk, but then >> it doesn't make sense at all. >> > >> > Any thoughts? >> > _______________________________________________ >> > Spacewalk-list mailing list >> > [email protected] >> > https://www.redhat.com/mailman/listinfo/spacewalk-list >> >> -- >> Oracle <http://www.oracle.com> >> Avi Miller | Product Management Director | +61 (3) 8616 3496 >> Oracle Linux and Virtualization >> 417 St Kilda Road, Melbourne, Victoria 3004 Australia >> >> >> _______________________________________________ >> 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 > > > -- > Oracle <http://www.oracle.com> > Avi Miller | Product Management Director | +61 (3) 8616 3496 > Oracle Linux and Virtualization > 417 St Kilda Road, Melbourne, Victoria 3004 Australia > > > _______________________________________________ > 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
