| Commit message (Collapse) | Author | Age | Files | Lines |
|
|
|
|
|
|
|
|
| |
As of March 31st 2019, SLES 11 is no longer generally supported. Per our
support process we will no longer officially support SLES 11.
See https://docs.chef.io/platforms.html#platform-end-of-life-policy
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Cleanup of habitat/plan.sh for chef-infra-client
|
| |
| |
| |
| | |
Signed-off-by: Salim Afiune <afiune@chef.io>
|
| |
| |
| |
| | |
Signed-off-by: Salim Afiune <afiune@chef.io>
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\ \
| | |
| | | |
Bump inspec-core-bin to 4.10.4 and Ohai to 15.2.4
|
| | |
| | |
| | |
| | | |
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|/ /
| |
| |
| |
| |
| | |
This pull request was triggered automatically via Expeditor when inspec-core-bin 4.10.4 was promoted to Rubygems.
This change falls under the obvious fix policy so no Developer Certificate of Origin (DCO) sign-off is required.
|
|\ \
| |/
|/| |
[ci] Fix omnibus pipeline
|
| |
| |
| |
| |
| |
| |
| | |
Fix platform names in release.omnibus.yml to conform with what
the new package publishing code in the omnibus gem expects.
Signed-off-by: Jeremiah Snapp <jeremiah@chef.io>
|
|/
|
|
|
|
|
| |
A new version of omnibus is required and the artifactory gem
is required for the publish part of the build stage.
Signed-off-by: Jeremiah Snapp <jeremiah@chef.io>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Remove Travis / Jenkins config / docs
|
| |
| |
| |
| |
| |
| | |
Update some of our build docs to reflect the current process. Nuke the old Travis config. We're Buildkite + appveyor only at this point.
Signed-off-by: Tim Smith <tsmith@chef.io>
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\ \
| |/
|/| |
Bump mixlib-shellout to 3.0.7
|
|/
|
|
|
|
| |
This pull request was triggered automatically via Expeditor when mixlib-shellout 3.0.7 was promoted to Rubygems.
This change falls under the obvious fix policy so no Developer Certificate of Origin (DCO) sign-off is required.
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Enable Kitchen dockken tests with BK linux executor
|
| |
| |
| |
| | |
Signed-off-by: Jaymala Sinha <jsinha@chef.io>
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\ \
| |/
|/| |
Jsinha/add rhel8
|
| |
| |
| |
| | |
Signed-off-by: Jaymala Sinha <jsinha@chef.io>
|
|/
|
|
| |
Signed-off-by: Jaymala Sinha <jsinha@chef.io>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Fix zypper test failures
|
|/
|
|
|
|
|
|
| |
Resolve error from kill for leftover rspec processes
Cloud testers have as many as 10 zypper repos configured and enabled, so the zypper searches from specs take longer to run on our testers as too many repos with most of them enabled were slowing down the zypper process, locking it during the test runs and failing the zypper package functional tests. Since we do not use these repos in our testing we delete them.
Signed-off-by: Jaymala Sinha <jsinha@chef.io>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Tweak data collector exception handling
|
| |
| |
| |
| | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
a 404 is probably unlikely in any circumstance other than when the user
really does not intend to use the data collector at all (hosted,
automate 1, older chef servers, etc).
i don't know how you'd get into a situation where the user wanted to
setup the data collector against an automate 2 server, but the
data collector endpoint didn't exist -- presumably because they
accidentally pointed it at a valid old chef server accidentally, which
is going to be an incredibly infrequent edge condition.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|/
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
|
| |
This isn't Java and Net::HTTP can throw a billion things, so just rescue
(nearly) everything. I have a hard time imagining that there's a
failure here that we wouldn't want to ignore, other than the ones like
OOM thrown by Exception that indicate internal failures.
Also only throw the "this is normal" info message on 404s, other
responses like 500s should be warns even if it is set to ignore
failures (people with data collectors correctly setup need to know about
500s even if we keep going, since that is abnormal).
This also fixes a bug in handling exceptions like Timeout::Error which
do not have a response.code at all which would throw NoMethodError.
closes #8749
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Duration field in resource report needs to be String
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
Somehow this got converted to a bare integer in Chef-15 refactoring
which causes the server-side to reject it, so reverting back to the
old format.
Closes #8532
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
| |
| |
| | |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\ \
| |/
|/| |
Update bzip2 from 1.0.6 -> 1.0.8 to resolve CVEs
|
|/
|
|
|
|
|
| |
* bzip2recover: Fix use after free issue with outFile (CVE-2016-3189)
* Make sure nSelectors is not out of range (CVE-2019-12900)
Signed-off-by: Tim Smith <tsmith@chef.io>
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Bump train-core to 2.1.19
|
|/
|
|
|
|
| |
This pull request was triggered automatically via Expeditor when train-core 2.1.19 was promoted to Rubygems.
This change falls under the obvious fix policy so no Developer Certificate of Origin (DCO) sign-off is required.
|
|
|
|
| |
Obvious fix; these changes are the result of automation not creative thinking.
|
|\
| |
| | |
Move chef-client and chef-solo shared code into a base class and remove duplication and skew
|
| |
| |
| |
| | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
| |
| |
| |
| |
| | |
this has to fix a bug for someone.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| |
| | |
most of these are options that apply to either chef-client -z or
to chef-solo without legacy mode, so they are justifiably common
options (that are handled by the trampolining into the Client
code from Solo right now.
the --legacy-mode switch is solo-specific (although we should wire it
up for chef-client eventually once all the code is merged).
old-reporting and skip-cookbook-sync only make sense for actual
chef-client runs so are marked as such in the help text
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
| |
| |
| |
| |
| |
| |
| | |
should fix fips mode for chef-solo, adds the windows admin check
feature, but the distable-config option needs some future work to the
base class to support it.
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| |
| |
| |
| | |
Signed-off-by: Lamont Granquist <lamont@scriptkiddie.org>
|
| | |
|