| Commit message (Collapse) | Author | Age | Files | Lines |
|---|
| |
|
|
|
|
|
|
|
|
|
|
| |
- this is compatible with gem versions from 11.6.0 with minimal
changes.
- mixlib-shellout differs in windows-versus-unix due to version pinning
in windows-pr picking up old mixlib-shellout on windows, this is
not fixed, and left similar to 11.6.0
- gem versions should be levelled up for 11.8.x and beyond
- newly built 11.6.0 will pick up new mixlib-config 2.0 which is
a delta from the downloadable omnibus builds, 11.6.2 will not
pick up mixlib-config 2.0
|
| | |
|
| | |
|
| | |
|
| |
|
|
| |
- mixlib-config 2.0 is an 11.8 feature
|
| |
|
|
|
|
|
|
|
|
|
|
|
|
| |
- allows us to explicitly version pin in the gemspec on gem installs
rather than getting different behavior from 'gem install' and
'bundle install' (gemspec vs. Gemfile).
- the mingw deps had been in the Gemfile because it needed to be a
group since gemspecs do not have groups. this builds two different
gems for publication to rubygems instead.
- see mixlib-shellout for the prototype of where this has been done
(successfully).
Conflicts:
Gemfile
|
| | |
|
| | |
|
| |\
| |
| | |
CHEF-4422 Truncate cache paths for remote files
|
| | | |
|
| | | |
|
| | | |
|
| |/
|
|
| |
path length limits
|
| |\
| |
| |
| | |
Minimal fix for CHEF-4406 suitable for hotfix/patch release
|
| | |
| |
| |
| |
| | |
Fixes test failures on 32 bit platforms by correctly filtering 64
bit-only tests
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes CHEF-4406 http://tickets.opscode.com/browse/CHEF-4406
Calls to Chef::Provider::Template#template_location and #template_finder
will now correctly reference the Chef::Provider::TemplateFinder class.
Chef::Provider::Package#preseed_resource uses these methods expecting an
error to be raised only if there is no template with the desired name,
which triggers a fallback to cookbook_file-based preseed files.
This patch restores the template-based preseed functionality, but will
trigger deprecation warnings from within Chef::Provider::Package's
internal code.
|
| | |
| |
| |
| | |
Repro/regression test for CHEF-4406 included but is marked pending.
|
| |/ |
|
| |\
| |
| | |
CHEF-4419: Absolute file paths with no drive letter for file resources on Windows fails chef-client run
|
| | | |
|
| | |
| |
| |
| | |
to the path if it starts with '/' in the most common code path we're encountering this issue.
|
| |/ |
|
| | |
|
| | |
|
| |\
| |
| | |
[CHEF-4380] Fix missing include on shellout mixin
|
| |/ |
|
| | |
|
| | |
|
| |\
| |
| | |
Change error description sections elements to be hashes.
|
| | |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
It is much easier for erlang to validate the json that chef-client sends up if exception_data.description.sections is of structure:
[{"str1" => "value1"}, ... ]
As opposed to current structure of:
[["str1", "value1"], ... ]
This change was achieved by updating error_description.rb. I also updated relevant test.
|
| |\ \ |
|
| | | | |
|
| | | | |
|
| | |\ \ |
|
| | | | | |
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Since the existing tests mocked out Resource#cookbook_version it missed
the case where if Resource#cookbook_name is nil then cookbook_version would
also be nil.
Added guard logic around setting the cookbook_name, cookbook_version
in resource_reporter.rb to protect against the case where cookbook_name
is nil.
|
| | |\ \ |
|
| | | | | |
|
| | |/ / |
|
| | |\ \ |
|
| | |/ /
| | |
| | |
| | |
| | |
| | |
| | |
| | |
| | | |
Fixes CHEF-4365: http://tickets.opscode.com/browse/CHEF-4365
A corrupt cache control file will cause a persistent failure of the
related remote_file resource. Since this data is just a cache of HTTP
headers, Chef can ignore corrupted cache control data, re-download the
source file, and then re-populate the cache with not-corrupt data.
|
| | |\ \
| | |/
| |/| |
Increase the default yum timeout to 5 minutes.
|
| | | | |
|
| | |/ |
|
| | |\ |
|
| | | | |
|
| | |/
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Fixes CHEF-4357: http://tickets.opscode.com/browse/CHEF-4357
Rescue exceptions from within a forker worker and feed them to
`Chef::Application.debug_stacktrace()`, then exit non-zero. This fixes
an issue where Chef would spew ruby stacktraces with forking enabled
(stacktraces should only be printed to console with `-l debug`).
Additionally fixes an issue where a generic exception was passed to
`debug_stacktrace`, leaving a stacktrace.out file with no useful
information.
In addition to the above fixes, includes the following improvements:
* Update the forked worker's argv0 to clearly indicate it's the worker
process, and include ppid and run start time.
* When reaping the worker process, include more useful information when
the worker exited non-successfully, such as exit code or signal that
killed the process. In particular, OOM kill (e.g., when running
resource intensive code compile, etc. on small machine) should be a
little more obvious.
|
| | | |
|
| | | |
|
| | |\
| | |
| | | |
this should have been reverted to old behavior, causes failures on
|
