| Commit message (Collapse) | Author | Age | Files | Lines |
... | |
| |/
|/|
| |
| | |
why I removed it, since the information in it isn't anywhere else.
|
|/ |
|
|
|
|
| |
Also reformatted a bit
|
| |
|
| |
|
|
|
|
|
|
|
| |
evaluation time, rather than resource instantiation time. This
means that you don't catch your "errors" as early, but it also
means you should be able to realistically configure a whole host
in one run.
|
|
|
|
|
| |
executable, since it otherwise causes caches to be used in all
cases, which we don't want (e.g., bin/puppet was using them).
|
|
|
|
|
|
| |
having it be a parameter. This is only useful if you want
a composite resource that just generates other resources and
passes the value on.
|
|
|
|
|
| |
server now that it's in the :puppetmasterd section rather than
a separate :yaml section.
|
|
|
|
|
|
|
| |
There is now a constant in Puppet::Network::HttpPool that will
disable or enable this feature, but note that we determined
that it can cause corruption, especially in file serving (but
it's client-side corruption).
|
|
|
|
| |
matching. The actual problem was caused by the fix to #1001.
|
| |
|
|
|
|
|
|
|
|
|
|
| |
any local variables and added a local variable -- see
http://snurl.com/21zf8. My own testing showed that this
caused memory growth to level off at a reasonable level.
Note that the link above says the problem is only with class
methods, but my own testing showed that it's any method that
meets these criteria. This is not a functional change, but
should hopefully be the last nail in the coffin of #1131.
|
|
|
|
|
|
|
|
|
|
| |
files, thanks to work by Adam Jacob and Arjuna Christenson
(the finding, not the leak). I'm going to act like this
fixes #1131, at least for now, but I doubt it does,
since that shows general memory growth over time, whereas
the leak here should go away as soon as files are reparsed
(because the parser is holding the reference to the leaking
array).
|
|
|
|
|
|
| |
date if the node facts have been updated (thus causing
node facts to again be available in manifests, for those
cases where they were not).
|
|
|
|
| |
388cf7c3df7ce26e953949ed6fe63d76cbbb3691 to resolve #1137; also, add tests which detect the problem.
|
| |
|
| |
|
|
|
|
| |
password management
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
Previously, if there were an error creating a resource,
the error would propagate leaving any previously
created resources still in memory.
Now, resources are removed by default when an error
happens during instantiation, and the error propagates
to the caller so that they can log or whatever.
This also allows the Settings class to correctly and
separately handle the cases where we can't create the
catalog (which should never happen in normal usage but
was happening because of this error -- later catalogs
couldn't be created because earlier catalogs left
resources lying around) from those where we can't
apply the catalog.
|
| |
|
|
|
|
| |
once, which should make the system a bit more efficient.
|
|
|
|
| |
This was obsoleted in 0.24.2.
|
| |
|
|
|
|
|
|
| |
(#1036). The problem only cropped up if there was a failure
when trying to manage the system -- this would cause the
setting-based resources not to get cleaned up.
|
|\ |
|
| | |
|
| |
| |
| |
| |
| | |
as the version for a node, which should similarly encourage the
use of the yaml cache. (Related to #1130)
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
cause ever-larger memory growth), and changing the external node
terminus to use the version of the facts as their version. This
will usually result in the cached node information being used,
instead of always hitting the external node app during file
serving. Note that if the facts aren't changed by the client,
then this will result in the cached node being used, but at this
point, the client always updates its facts. (#1130)
|
| |
| |
| |
| | |
of the yaml file as the version of the object.
|
|/ |
|
|
|
|
| |
When :node_name="cert" is specified the 'hostname' fact should be set to the SSL certificate common name instead of the results from facter. I've extended this to also set 'domain' and 'fqdn' since that makes a lot of sense to me. This fixes a regression introduced in SVN#1673
|
|
|
|
| |
Fixes #1086
|
|
|
|
| |
(Patch by freiheit.)
|
|
|
|
|
|
| |
Note that this changes the behaviour a bit -- the resource's
noop setting always beats the global setting (previously,
whichever was true would win).
|
| |
|
| |
|
|\ |
|
| |
| |
| |
| |
| |
| | |
Replace the catalog with the newly created one when converting to ral types.
The aliases were being lost because the resources had references to the old catalog being converted
|
| | |
|
|\ \ |
|
| | | |
|
| | |
| | |
| | |
| | | |
This reverts commit ca0b62a0f8be88bf3dc33df6b2437d8105a71cea.
|
| | | |
|
| | |
| | |
| | |
| | | |
an environment and Puppet will now use it.
|
| | |
| | |
| | |
| | | |
and the schema has been updated accordingly.
|
|\ \ \
| | |/
| |/| |
|
| |/
| |
| |
| |
| |
| |
| |
| |
| |
| | |
The CA serial file was getting owned by root because it was using a different method to write to file
Pulled the readwritelock out of lib/puppet/sslcertificates/ca.rb into lib/puppet/util/settings.rb
Refactored write, writesub and readwritelock a bit to reuse code
(write and readwritelock both call writesub)
Added a mode to :serial in lib/puppet/util/defaults.rb
|
|\ \ |
|