Hi,
= the best way to help get this fixed is probably to test the
proposed patches and to report back here :)
By the way, we're running a production puppetmaster with the patches and
everything (db creation, stored configs and exported resource
collection) works fine. I'll commit the
bertagaz wrote (11 Mar 2015 11:17:48 GMT) :
I've just build the puppet* packages from Jessie with the last patch from this
thread,
Great news that you confirm it works!
If any other can test it, please do so.
I believe it would be more beneficial to test the patch that was
attached to the
Hi all,
On 22:16 Sun 08 Mar , intrigeri wrote:
= the best way to help get this fixed is probably to test the
proposed patches and to report back here :)
By the way, we're running a production puppetmaster with the patches and
everything (db creation, stored configs and exported resource
Control: severity -1 serious
Also, since all major Puppet setups I know of use AR-based stored
configs and exported resources, I think this is a major regression from
wheezy and warrants a severity: serious.
Regards,
Apollon
signature.asc
Description: Digital signature
Hi Gabriel,
Gabriel Filion wrote (08 Mar 2015 20:14:01 GMT) :
We really do need to find a solution to this issue before jessie is
released (or in the worst case, at first point release).
A patch series has been proposed (thanks Apollon!):
Hey there,
Sorry if I'm jumping in late, but I'd like to weigh in the importance of
storedconfigs. Even though it's an optional feature, the biggest
majority of users need to use it in order to have a functional setup.
For comparison, releasing without it would be like releasing apache
without
Hi,
On Mon, 2 Mar 2015 17:18:18 +0100 Christian Hofstaedtler z...@debian.org
wrote:
IMO, nothing of value has been lost, and the only thing that should
probably be done is a NEWS/RelNotes entry (which likely is required
anyway, I seriously doubt upgrading inplace from 2.7 to 3.7 does
yield
Apollon Oikonomopoulos apoi...@debian.org writes:
Then for Puppet 4/5/whatever we definitely need to provide a PuppetDB
package.
To package puppetdb while following the Debian packaging policy,
experience with packaging clojure or java apps for Debian with leiningen
and maven would be a big
Just a small update to the patch, to fix database creation.
lib/puppet/rails/database/schema.rb contains a lot of:
add_index blah, :integer = true
statements. The :integer = true option to add_index method is not documented
anywhere, not even in the earliest versions of ActiveRecord. Up to
On Mon, Mar 2, 2015 at 6:09 PM, micah mi...@debian.org wrote:
Christian Hofstaedtler z...@debian.org writes:
[CUT]
The thing is, one really does not want to use Puppet with
storedconfigs with activerecord (it's unbearably slow).
I disagree, I want to use Puppet with storedconfigs and
* intrigeri intrig...@debian.org [150209 16:03]:
tl;dr for Debian Ruby Extras maintainers: in Jessie, Puppet's
storeconfig feature can either use activerecord (deprecated, only
works with activerecord 3.x, broken with activerecord 4.x) or PuppetDB
(not packaged in Debian yet). So, currently we
Hi,
Christian Hofstaedtler wrote (02 Mar 2015 16:18:18 GMT) :
The thing is, one really does not want to use Puppet with
storedconfigs with activerecord (it's unbearably slow).
Thanks for sharing your opinion on this topic.
Let me share my experience and preferences. I've been using
Christian Hofstaedtler z...@debian.org writes:
* intrigeri intrig...@debian.org [150209 16:03]:
tl;dr for Debian Ruby Extras maintainers: in Jessie, Puppet's
storeconfig feature can either use activerecord (deprecated, only
works with activerecord 3.x, broken with activerecord 4.x) or
On 12:10 Sat 28 Feb , Apollon Oikonomopoulos wrote:
Note that you have to install ruby-activerecord-deprecated-finders.
By the way, I wonder if puppetmaster-common should Recommend (or at
least Suggest) ruby-activerecord and
ruby-activerecord-deprecated-finders. If not, we should at least
Hi,
It should be possible to make Puppet work with ActiveRecord 4.x. I've
managed to get it to a point where it doesn't throw exceptions, but I
have to verify that's it's actually doing what it should do.
In short, what's been needed sofar is:
- verify_active_connections! must be replaced
Hi,
Apollon Oikonomopoulos wrote (28 Feb 2015 08:29:14 GMT) :
- installing ruby-activerecord-deprecated-finders makes find(:all) work
again but throws a ton of deprecation warnings. I'd prefer
forward-porting all queries to the rails 4 API.
I agree it would be nicer from a
Control: tags -1 patch
The attached patch works for me. I did a test using
`puppet master --compile` for a given host and cross-checked the entries
with those on my real puppet master and everything seems to be working
fine. Also, exported resources are now being collected.
If anyone can,
Hi,
intrigeri wrote (09 Feb 2015 15:02:36 GMT) :
Adding the previous maintainers of ruby-activerecord-3.2 into the
loop, in case they have an idea. E.g. would it be an option to
reintroduce the 'verify_active_connections!' method from 3.2 into
Jessie's ActiveRecord::Base:Class? (I guess not,
Hi,
intrigeri wrote (09 Feb 2015 15:11:38 GMT) :
Another lead might be to reintroduce ruby-activerecord-3.x into
Jessie(!). Apparently it also involves getting a compatibility patch
back into ruby-arel, that was removed in the 5.0.1.20140414130214-1
upload. Before I test this: is there any
Hi,
Russ Allbery wrote (10 Feb 2015 02:59:15 GMT) :
intrigeri intrig...@debian.org writes:
This sounds RC to me. [...]
Well, it's RC in the sense that it's a pretty serious regression, but it's
an optional feature in Puppet and it's entirely possible to use Puppet
without using storedconfig
intrigeri wrote (09 Feb 2015 15:02:36 GMT) :
E.g. would it be an option to
reintroduce the 'verify_active_connections!' method from 3.2 into
Jessie's ActiveRecord::Base:Class? (I guess not, but if it is, then it
would possibly be the easiest way forward.)
Another lead might be to reintroduce
Hi,
tl;dr for Debian Ruby Extras maintainers: in Jessie, Puppet's
storeconfig feature can either use activerecord (deprecated, only
works with activerecord 3.x, broken with activerecord 4.x) or PuppetDB
(not packaged in Debian yet). So, currently we have a serious
regression on the Wheezy-Jessie
intrigeri intrig...@debian.org writes:
For the record, what's been replied there is that Puppet 3.7 needs
activerecord 3.x (found in Wheezy) for storeconfig to work without
puppetdb, while Jessie has activerecord 4.1.8, and ruby-activerecord-3.2
has been removed from unstable in May, 2014.
On 2015-02-02 20:11, micah wrote:
David Mohr b...@da.mcbf.net writes:
Is noone using puppet in jessie with storeconfigs? That seems really
odd
to me...
Unfortunately, all my puppet recipes are on nothing newer than wheezy
right now, and need some serious tending to before they can get to
I'm also struggling to understand what the issue is. I need
storedconfigs, but puppetdb is not packaged, and it seems that the
version of activerecord in jessie is too new for puppet, because
according to
http://apidock.com/rails/ActiveRecord/Base/verify_active_connections!/class
that method
David Mohr b...@da.mcbf.net writes:
Is noone using puppet in jessie with storeconfigs? That seems really odd
to me...
Unfortunately, all my puppet recipes are on nothing newer than wheezy
right now, and need some serious tending to before they can get to using
the newer version so I haven't
26 matches
Mail list logo
