Looks like it got missed when installing puppet on the already-cloned VMs.
The epel repository does have anymore the 0.24.8 version of puppet that we have and I had to modify the install steps that I mention in: https://bugzilla.mozilla.org/show_bug.cgi?id=505232#c9 wget http://linux.web.psi.ch/dist/scientific/5/beta/puppet-0.24.8-1.el5.1.noarch.rpm rpm -i puppet-0.24.8-1.el5.1.noarch.rpm I will leave the slave on staging for few days to see how it behaves.
I left the machine running but it was not being able to upload anything to staging-stage (waiting on adding to known_hosts). I will leave it for another night.
Perhaps we should be keeping a copy of the the puppet package somewhere ? The private CVS repo would be a candidate.
I have put the slave back into the pool. (In reply to comment #3) > Perhaps we should be keeping a copy of the the puppet package somewhere ? The > private CVS repo would be a candidate. Done. [root@staging-puppet dist]# cvs add puppet-0.24.8-1.el5.1.noarch.rpm cvs add: scheduling file `puppet-0.24.8-1.el5.1.noarch.rpm' for addition cvs add: use 'cvs commit' to add this file permanently [root@staging-puppet dist]# pwd /N/puppet-files/dist [root@staging-puppet dist]# cvs ci -m "Bug 560908. Store puppet 0.24.8. r=bhearsum" cvs commit: Examining . RCS file: /mofo/puppet-files/dist/puppet-0.24.8-1.el5.1.noarch.rpm,v done Checking in puppet-0.24.8-1.el5.1.noarch.rpm; /mofo/puppet-files/dist/puppet-0.24.8-1.el5.1.noarch.rpm,v <-- puppet-0.24.8-1.el5.1.noarch.rpm initial revision: 1.1 done
Please use the '-kb' flag when adding binary files to CVS!
The machine was moved to production for quite some time. Closing since it is all done in here.