-----BEGIN PGP SIGNED MESSAGE-----
Hash: SHA1
Hi
First, I would like to thank for that open process and the commitment
you are putting into that. And I'm really excited that there is now a
team dedicated to address the things in core puppet. Awesome! Thanks!
However, as this thread seemed to become more and more a "Please, fix
that bug"-list, I would like to tell my story as well:
>> I hope this gets resolved too, but the bug ticket says it was pushed to
>> 2.8.x
>
>
> I asked the core developers to spend some time investigating it a while ago
> to see if we could fix it in 2.6.x, but the report was that this would
> require significant enough plumbing changes that it needs to be done for a
> feature release, and we didn't get it into 2.7.x
>
> If there's an appropriate middle ground we can hit for a solution, I'd love
> to target it earlier if possible.
in the last two days I was bootstrapping a new puppet environment at a
customer's place and I ran into some wtf's of problems I had forgotten
or I haven't encountered so far.
But for nearly every issue I could find a (long) outstanding bug report.
Most of them are about puppet acting in a unexpected way aka ignoring
the principle of last surprise. As usual there are people who started to
depend on that behavior and now we need to make it configurable and the
idea is to wait for a new major release so we can introduce a behavior
change while switching to the more expected way.
None of them seem to be fixed so far for 2.7, so my assumption is that
we have to wait till the next one. :/
Often there are workarounds available or they are not that severe, so
one can live with them. But still: things are broken.
I know we are a bit late to the 2.7 release game, but I still would like
to raise my concerns that to me it sometimes looks like a lot of these
bugs seem to get forgotten more and more and are getting burried within
progress and the available workarounds. But still: things are broken.
I'm going to comment on these bug reports.
One of the major ones I found is that filebucketing is broken (since a
year):
#5362 [1] & #3807 [2] - I really had to do the following to get
filebuckets to the master:
filebucket{main:
path => false,
server => puppet,
}
File{ backup => main }
filebucket's got recently some improvements like getting a diff and
displaying the buckets in the dashboard is quite a nice feature. But the
underlying puppet feature is broken for over a year?
Imho this should get the attention it deserves for 2.7.
Actually, I wanted to do here another "rant" about ENC acting weird, but
while doing more research I actually found a couple of other bug reports
all talking about the same and also one where it looks like this is
going to be fixed. But the history of back and forth is quite amazing :/ ...
So I will link all these bug reports together so you can decide which
one is actually still valid.
I hope you understand my point, otherwise please ask!
Thanks!
~pete
[1] http://projects.puppetlabs.com/issues/5362
[2] http://projects.puppetlabs.com/issues/3807
-----BEGIN PGP SIGNATURE-----
Version: GnuPG v1.4.11 (GNU/Linux)
Comment: Using GnuPG with Mozilla - http://enigmail.mozdev.org/
iEYEARECAAYFAk3mi30ACgkQbwltcAfKi3+bRwCfY4qnlHA8AtYCHEjMZKIyW7Y5
CC4AoKp3AU3FTuD3LN4G9pzdUGr23h/c
=Inz9
-----END PGP SIGNATURE-----
--
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+unsubscr...@googlegroups.com.
For more options, visit this group at
http://groups.google.com/group/puppet-users?hl=en.
