Puppet users - Nov 2010 - updating kernel in centos shows failure

I wanted to use puppet to update my kernel.  Afterwards I wanted to
reboot the computer.   I''m using centos5.5.

Googling around I came up with this:

  exec { rebootDueToPackageUpdates:
    command => "/sbin/reboot",
    refreshonly => "true"
  }
  package { "kernel":
    ensure => "2.6.18-194.17.4.el5",
    notify => Exec[rebootDueToPackageUpdates]
  }

When it runs I see an error, even though the new version is
installed.  Because the old version still exists (I''m guessing), it
determines it failed:

.../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

I can only assume the package type doesn''t deal with the special case
of the ''kernel'' package always doing an install rather than an
update.  This may be a rpm/redhat/centos specific thing...

Is my assessment wrong?  Anybody got ideas how to do this maybe w/o
package?  Do I really have to resort to an exec onlyif test for
missing version?  Seems messy...  Seems like something the rpm
provider for package should handle as any rpm install of
''kernel'' is
always an install and not an update.

Thanks,
Steve

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

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

-- 

Trevor Hemsley
Infrastructure Engineer
.................................................
* C A L Y P S O
* 4th Floor, Tower Point,
44 North Road,
Brighton, BN1 1YR, UK   

OFFICE 	+44 (0) 1273 666 350
FAX 	+44 (0) 1273 666 351

.................................................
www.calypso.com

This electronic-mail might contain confidential information intended 
only for the use by the entity named. If the reader of this message is 
not the intended recipient, the reader is hereby notified that any 
dissemination, distribution or copying is strictly prohibited.

* P * /*/ Please consider the environment before printing this e-mail /*/

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

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

-- 

Trevor Hemsley
Infrastructure Engineer
.................................................
* C A L Y P S O
* 4th Floor, Tower Point,
44 North Road,
Brighton, BN1 1YR, UK   

OFFICE 	+44 (0) 1273 666 350
FAX 	+44 (0) 1273 666 351

.................................................
www.calypso.com

This electronic-mail might contain confidential information intended 
only for the use by the entity named. If the reader of this message is 
not the intended recipient, the reader is hereby notified that any 
dissemination, distribution or copying is strictly prohibited.

* P * /*/ Please consider the environment before printing this e-mail /*/

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

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-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

R P Herrold 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
When I ran into this bug it was because I had ensure => latest specified 
for the package name and the intent was to have puppet install the 
latest kernel RPM and notify me that it had been done so I could 
schedule a reboot. Most of the time I want the latest kernel installed 
and puppet cannot handle the way that kernels (installonly) packages 
work on RHEL + clones.

-- 

Trevor Hemsley
Infrastructure Engineer
.................................................
* C A L Y P S O
* 4th Floor, Tower Point,
44 North Road,
Brighton, BN1 1YR, UK   

OFFICE 	+44 (0) 1273 666 350
FAX 	+44 (0) 1273 666 351

.................................................
www.calypso.com

This electronic-mail might contain confidential information intended 
only for the use by the entity named. If the reader of this message is 
not the intended recipient, the reader is hereby notified that any 
dissemination, distribution or copying is strictly prohibited.

* P * /*/ Please consider the environment before printing this e-mail /*/

-- 
You received this message because you are subscribed to the Google Groups
"Puppet Users" group.
To post to this group, send email to puppet-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.

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-users@googlegroups.com.
To unsubscribe from this group, send email to
puppet-users+unsubscribe@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.