On Sun, Oct 14, 2012 at 11:27 AM, Jakov Sosic wrote:

On 10/08/2012 09:21 PM, Jeff McCune wrote:

I hope this helps and thank you again for reporting this issue,
I think the easiest way of handling this issue is to have different
repositories for different versions of puppet.
I would certainly +1 this method! I was bitten by the puppet 3.x packages
for 2 reasons. The first one is that in my kickstart configs, I have
"puppet" specified as a package which gets installed during installation
and performs some trickery to run Puppet for the first time on the client,
and get the certificate signed. As Puppet 3.x was now being installed by
yum, it broke our installations. My workaround was to set "puppet-2.7" in
the kickstart file, but far from ideal :(

I was then bitten by Puppet doing what it's supposed to do :) As I had
ensure => latest for the Puppet client, it went around and upgraded a lot
of my clients to 3.x, which broke things. I guess I never expected such
incompatible packages to be made available in the puppetlabs yum repo, but
there's always a first :)

It looks like Puppetlabs are well aware of this issue, so I look forward to
the resolution. Personally, I think packages should be grouped in a logical
manner, so that any package in the group will not (or should not) break
functionality if upgraded.

- Gonzalo

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.

Search Discussions

Discussion Posts


Follow ups

Related Discussions



site design / logo © 2022 Grokbase