Hello all,
I have puppet rpm on internal repository for updating it to servers that
don''t have it on their normal repos (Centos, Fedora Core 4 or older...)
Then I have this to ensure that puppet is at latest version:
package { "puppet":
ensure => latest,
provider => yum,
}
I added puppet 0.22.3 to my internal repository and all servers updated
to that version, but I''m receiving reports like this:
ensure changed ''0.22.3-1'' to ''0.20.0-1.fc4''
Here the logs of one of the servers (CentOS 4.3) at the update moment:
puppetd[16126]: Starting configuration run
yum: Updated: puppet.i386 0.22.3-1
puppetd[16126]: (//mynode.com/anynode/Package[puppet]/ensure) ensure
changed ''0.22.2-1'' to ''0.22.3-1''
puppetd[16126]: Finished configuration run in 78.08 seconds
puppetd[16126]: Starting configuration run
puppetd[16126]: (//mynode.com/anynode/Package[puppet]/ensure) ensure
changed ''0.22.3-1'' to ''0.18.4-2.el4.kb''
puppetd[16126]: Finished configuration run in 52.50 seconds
Puppet updated to the new version in all servers, but are reporting a
change to older version every time puppet runs (but puppet stays at new
version).
Can I safely ignore that messages?
On Fri, 2007-04-13 at 12:53 +0200, Lluis Gili wrote:> Here the logs of one of the servers (CentOS 4.3) at the update moment: > > puppetd[16126]: Starting configuration run > yum: Updated: puppet.i386 0.22.3-1 > puppetd[16126]: (//mynode.com/anynode/Package[puppet]/ensure) ensure > changed ''0.22.2-1'' to ''0.22.3-1'' > puppetd[16126]: Finished configuration run in 78.08 seconds > > puppetd[16126]: Starting configuration run > puppetd[16126]: (//mynode.com/anynode/Package[puppet]/ensure) ensure > changed ''0.22.3-1'' to ''0.18.4-2.el4.kb'' > puppetd[16126]: Finished configuration run in 52.50 seconds > > Puppet updated to the new version in all servers, but are reporting a > change to older version every time puppet runs (but puppet stays at new > version). > > Can I safely ignore that messages?What packages wind up being installed on those machines after puppet''s run ? Also, what does a ''yum update puppet'' say it wants to do when you run it manually ? I am hoping that it''s simply an issue with printing the wrong version numbers, though it might be something else. David
No changes are made when puppet runs, puppet stays at version 0.22.3 runing ''yum update puppet'' says ''Could not find update match for puppet'' I have other package installed from internal repository without any problem, might be because there''s no other version in official repositories, seems that puppet can''t know which version is the newest Lluís. El vie 13 de 04 del 2007 a les 09:30 -0700, en/na David Lutterkort va escriure:> On Fri, 2007-04-13 at 12:53 +0200, Lluis Gili wrote: > > Here the logs of one of the servers (CentOS 4.3) at the update moment: > > > > puppetd[16126]: Starting configuration run > > yum: Updated: puppet.i386 0.22.3-1 > > puppetd[16126]: (//mynode.com/anynode/Package[puppet]/ensure) ensure > > changed ''0.22.2-1'' to ''0.22.3-1'' > > puppetd[16126]: Finished configuration run in 78.08 seconds > > > > puppetd[16126]: Starting configuration run > > puppetd[16126]: (//mynode.com/anynode/Package[puppet]/ensure) ensure > > changed ''0.22.3-1'' to ''0.18.4-2.el4.kb'' > > puppetd[16126]: Finished configuration run in 52.50 seconds > > > > Puppet updated to the new version in all servers, but are reporting a > > change to older version every time puppet runs (but puppet stays at new > > version). > > > > Can I safely ignore that messages? > > What packages wind up being installed on those machines after puppet''s > run ? Also, what does a ''yum update puppet'' say it wants to do when you > run it manually ? I am hoping that it''s simply an issue with printing > the wrong version numbers, though it might be something else. > > David > >