| Age | Commit message (Collapse) | Author | Files | Lines |
|---|
|
|
|
|
|
Closes: #722614
|
|
Closes: #721772
These tests are separate, and should be run within a framework that restores
the testbed between tests. The "breaks-testbed" keyword for autopkgtest looked
promising, but didn't work as expected.
|
|
Closes: #714202
Thanks: Michael Stapelberg
|
|
|
|
|
|
Upstream version 3.3.0
|
|
|
|
|
|
|
|
(maint) ignore Gemfile.local
|
|
|
|
- "puppet apply" gets really unhappy when hiera is missing, so this is not
only used by the puppet master, but is also required for standalone puppet.
|
|
- remove "rdoc", it is a virtual package provided by "ruby"
- remove version on the "sysv-rc" dependency, there is no sysv-rc that old in
debian anymore.
|
|
- used by gem2deb, which we no longer use for packaging
|
|
zaphod42/issue/stable/22383-mount-no-longer-allows-true-for-atboot
(#22383) Allow all boolean values for atboot
|
|
The previous restrictions placed on the atboot property for mount caused
some previously valid manifests to begin to fail. The problem stems from
the fact that atboot is only used on solaris, but can always be
specified by users. It used to be able to be nearly anything, but only
yes and no meant anything on solaris. This fixes the problem by
expanding the allowed values to include all of the "boolean" values as
expressed in the Puppet::[Parameter|Property]::Boolean type and using a
munge method to convert the boolean to the correct yes or no value.
|
|
* ticket/stable/22258-create-new-console:
(#22258) Create new console for each puppet run
|
|
Powershell apparently has some issue trying to share the Windows
service's console when running under ruby.exe (as opposed to rubyw.exe).
This patch causes the service to create a new console for each puppet
child it kicks off, which resolves the issue.
|
|
Docs: Clarify descriptions of "ordering" and "report_serialization_format" settings
|
|
joshcooper/ticket/stable/22375-filebucket-serialization
(#22375) File bucket serialization
|
|
settings
|
|
(#21427) make supported_formats return an array of symbols
|
|
Prior to this commit, supported_formats was returning an array of
strings, which violated the contract for FormatHandler's
most_suitable_format_for method. This commit fixes supported_formats
to return an array of symbols.
|
|
* issue/stable/21427-select-report-serialization-format:
(#21427) Handle loss of precision during YAML serialization
(#21427) Make report format selectable
|
|
Previously, when round-tripping a report using YAML, the
Puppet::Resource::Status#time object could lose precision (depending on
the ruby version and platform), so it did not match the expected value. For
example, the expected value was:
"time"=>"2013-09-04T17:01:38.510604415+00:00"
But the round-tripped value was:
"time"=>"2013-09-04T17:01:38.510604000+00:00"
This commit changes the test to explicitly compare status fields, and
handles the `time` field specially to avoid loss of precision during
YAML serialization.
|
|
Without making agents able to select the format to serialize reports, a
newer agent would be unable to submit reports to an older master.
Although we ask users to upgrade masters first, that is not often done
in practice. In order to allow those kinds of setups to work, this makes
the report format selectable.
Puppet 3.2.2 and later support reports as pson, so only older, insecure
masters need to have the agent's change this new setting.
|
|
Previously, when the agent backed up a file to the master, the master
would inadvertently echo the file back to the agent in the body of the
HTTP response.
This is because the terminus' save method returned the file contents
as the 'result', and when invoked via REST, the {webrick,rack} REST
handlers automatically write the result into the response body.
Also puppet masters prior to 3.3 did not respect the Accept HTTP
header (#21427), so the master would always YAML encode the response,
which for binary content, large files, etc could result errors like
the following on the master:
Error: Stack overflow in regexp matcher: /\A(?: # ?: non-capturing group (grouping with no back references)
[\x09\x0A\x0D\x20-\x7E] # ASCII
| [\xC2-\xDF][\x80-\xBF] # non-overlong 2-byte
| \xE0[\xA0-\xBF][\x80-\xBF] # excluding overlongs
| [\xE1-\xEC\xEE\xEF][\x80-\xBF]{2} # straight 3-byte
| \xED[\x80-\x9F][\x80-\xBF] # excluding surrogates
| \xF0[\x90-\xBF][\x80-\xBF]{2} # planes 1-3
| [\xF1-\xF3][\x80-\xBF]{3} # planes 4-15
| \xF4[\x80-\x8F][\x80-\xBF]{2} # plane 16
)*\z/mxn
This commit changes the Puppet::FileBucketFile::File terminus to
return a new model instance whose content is empty. This is a change
from previously when we were returning a string, but I think it's
clearer that the result needs to be serializable using one of the
Accept content-types that the client specified, e.g. `:s`.
Originally filed as #8229
|
|
Previously, agents would backup files using PSON serialization, which is
not reliable for binary content, and incredibly inefficient due to the
applying a regexp to the entire in-memory file content.
Ideally, I would like to switch the Puppet::FileBucket::File class to
just use the `:raw` serialization format as is done for
Puppet::FileServing::Content. But this cannot be done in a minor series
without breaking compatibility between newer 3.x agents talking to older
3.x masters.
However, we can achieve the same effect by using the `:s` serialization
format, and we don't have the same compatibility problem because
the `from_s` method has been defined since 2.6.0 in commit e5a78009f.
If a newer master receives a file bucket request from an older agent
that sends a PSON encoded file, then the master will generate a
deprecation warning to update the agent.
Originally filed as #8229.
|
|
zaphod42/issue/stable/22358-improper-handling-of-accept-headers
(#22358) Interpret */* as anything is accepted
|
|
|
|
|
|
The changes to how we process Accept headers left out the case of being
asked for anything (*/*), which the puppet dashboard will do. This
expands */* to mean the client accepts any format the the requested
endpoint can support.
In addition, this also adds logic to ignore quality specifiers.
|
|
(#19056) strip trailing space while parsing AIX password file
|
|
|
|
(Bug #22237) Remove EOL Fedora 17
|
|
|
|
jpartlow/issue/stable/22319-constrain-integration-spec-on-windows
(#22319) Constrain settings watchedfile integration on windows
|
|
File.ctime provides creation time on Windows, and shows no change in
WatchedFile. But we have no long running processes in Windows, so we
would not be reloading configs, and this test can be skipped.
|
|
Closes: #721132
|
|
Git-Dch: Ignore
|
|
|
|
jpartlow/issue/stable/22319-puppet-settings-misuses-watchedfile
(#22319) Correct Puppet::Setting's use of WatchedFile
|
|
zaphod42/issue/master/22229-ensure-generated-resources-contained
(#22229) Ensure generated resources contained
|
|
WatchedFile was introduced after 3.2.0 as a new method of checking for
changes to file. Puppet::Settings was calling a non-existent method on
the new WatchedFile, and would cause a daemonized Puppet to abort if one
of its watched configuration files was changed.
This is a minor change to call #to_str instead.
|
|
The catalog tracks the relationship between the container and the
contained resource but did not provide any clear way to query for the
containment information. This adds a new method #container_of(resource)
that will return the container of the given resource, when one exists.
This removes some duplication around understanding what the container
is.
|
|
The generated resources were left out in the cold with respect to
containers: they had none at all. This changes that to make sure that
the generated resources (via #generate and #eval_generate) have the same
container as the resource that generated them.
|
|
|
|
(#22250) ensure a failed resource status always has an event
|
