That only speaks to the initial install. Let's say in 6 months, I update my local mirror to a yet newer version of the kernel. I'm in the same boat.
The point of using a tool like Puppet, isn't just to automate your installs, but also upgrades. I'm surprised that this bug is this old, but it seems that it is targeted for the 'Statler' release. Of course, that assignment was 4 months ago so looks like I'll just take a wait and see approach. Steve On Nov 5, 4:37 pm, R P Herrold <herr...@owlriver.com> wrote: > On Fri, 5 Nov 2010, Trevor Hemsley wrote: > > Steve Hoffman wrote: > >> .../Package[kernel]/ensure) change from 2.6.18-194.el5 to > >> 2.6.18-194.17.4.el5 failed: Could not update: Failed to update to > >> version 2.6.18-194.17.4.el5, got version 2.6.18-194.el5 instead at ... > > >> # rpm -qa | grep kernel > >> kernel-2.6.18-194.el5 > >> kernel-2.6.18-194.17.4.el5 > > > This is a long standing bug that currently seems to have no action scheduled > > for it. > > >https://projects.puppetlabs.com/issues/1720 > > gee -- a two year old bug > > This 'issue' is readily solveable by a person running their > mirror locally of the desired content -- > > Upstreams retire content. If you are counting on being able > to access a specific version, run a mirror > > -- Russ herrold > herrold at centos dot org -- You received this message because you are subscribed to the Google Groups "Puppet Users" group. To post to this group, send email to puppet-us...@googlegroups.com. To unsubscribe from this group, send email to puppet-users+unsubscr...@googlegroups.com. For more options, visit this group at http://groups.google.com/group/puppet-users?hl=en.
