summaryrefslogtreecommitdiff
Commit message (Collapse)AuthorAgeFilesLines
* Bump version to 18.0.24 by Chef Expeditorv18.0.24Chef Expeditor2022-09-203-5/+6
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Merge pull request #1769 from chef/dependabot/bundler/rubocop-performance-1.15.0Marc A. Paradise2022-09-201-1/+1
|\ | | | | Update rubocop-performance requirement from 1.14.3 to 1.15.0
| * Update rubocop-performance requirement from 1.14.3 to 1.15.0dependabot[bot]2022-09-121-1/+1
|/ | | | | | | | | | | | | | Updates the requirements on [rubocop-performance](https://github.com/rubocop/rubocop-performance) to permit the latest version. - [Release notes](https://github.com/rubocop/rubocop-performance/releases) - [Changelog](https://github.com/rubocop/rubocop-performance/blob/master/CHANGELOG.md) - [Commits](https://github.com/rubocop/rubocop-performance/compare/v1.14.3...v1.15.0) --- updated-dependencies: - dependency-name: rubocop-performance dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
* Bump version to 18.0.23 by Chef Expeditorv18.0.23Chef Expeditor2022-09-063-5/+6
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Use a minimum of 1 thread per core for CPU total calculation (#1756)Stan Hu2022-09-065-8/+169
| | | | | | | | | | In some LXD containers running with VT-x hardware virtualization, it appears that threads per core is 0, resulting in a total number of CPUs of 0. Add a test case and handle some quirks with the `lscpu` output. Closes https://github.com/chef/ohai/issues/1755 Signed-off-by: Stan Hu <stanhu@gmail.com>
* Bump version to 18.0.22 by Chef Expeditorv18.0.22Chef Expeditor2022-08-303-5/+6
| | | | Obvious fix; these changes are the result of automation not creative thinking.
* Merge pull request #1761 from stanhu/sh-cpuinfo-fallbacktpowell-progress2022-08-301-4/+12
|\ | | | | Fall back to /proc/cpuinfo if lscpu doesn't have CPU totals
| * Fall back to /proc/cpuinfo if lscpu doesn't have CPU totalsStan Hu2022-08-241-4/+12
| | | | | | | | | | | | | | | | | | | | | | | | | | | | https://github.com/chef/ohai/pull/1454 made `lscpu` the primary way Ohai gathers CPU data, but the parser doesn't handle the output from a Raspberry Pi 4 Cortex-A72. For example, an ARM cluster has the output `Core(s) per cluster` instead of `Core(s) per socket`. We should fall back to `/proc/cpuinfo` if we don't get reasonable data back. It's not enough just to have `lscpu` output. Closes https://github.com/chef/ohai/issues/1760 Signed-off-by: Stan Hu <stanhu@gmail.com>
* | Bump version to 18.0.21 by Chef Expeditorv18.0.21Chef Expeditor2022-08-233-5/+6
| | | | | | | | Obvious fix; these changes are the result of automation not creative thinking.
* | Merge pull request #1757 from chef/dependabot/bundler/rubocop-performance-1.14.3Marc A. Paradise2022-08-231-1/+1
|\ \ | | | | | | Update rubocop-performance requirement from 1.14.2 to 1.14.3
| * | Update rubocop-performance requirement from 1.14.2 to 1.14.3dependabot[bot]2022-07-181-1/+1
| |/ | | | | | | | | | | | | | | | | | | | | | | | | | | Updates the requirements on [rubocop-performance](https://github.com/rubocop/rubocop-performance) to permit the latest version. - [Release notes](https://github.com/rubocop/rubocop-performance/releases) - [Changelog](https://github.com/rubocop/rubocop-performance/blob/master/CHANGELOG.md) - [Commits](https://github.com/rubocop/rubocop-performance/compare/v1.14.2...v1.14.3) --- updated-dependencies: - dependency-name: rubocop-performance dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
* | Bump version to 18.0.20 by Chef Expeditorv18.0.20Chef Expeditor2022-08-093-5/+6
| | | | | | | | Obvious fix; these changes are the result of automation not creative thinking.
* | Merge pull request #1752 from chef/dependabot/github_actions/actions/checkout-3Marc A. Paradise2022-08-093-3/+3
|\ \ | | | | | | Bump actions/checkout from 2 to 3
| * | Bump actions/checkout from 2 to 3dependabot[bot]2022-06-143-3/+3
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Bumps [actions/checkout](https://github.com/actions/checkout) from 2 to 3. - [Release notes](https://github.com/actions/checkout/releases) - [Changelog](https://github.com/actions/checkout/blob/main/CHANGELOG.md) - [Commits](https://github.com/actions/checkout/compare/v2...v3) --- updated-dependencies: - dependency-name: actions/checkout dependency-type: direct:production update-type: version-update:semver-major ... Signed-off-by: dependabot[bot] <support@github.com>
* | | Bump version to 18.0.19 by Chef Expeditorv18.0.19Chef Expeditor2022-08-093-5/+6
| | | | | | | | | | | | Obvious fix; these changes are the result of automation not creative thinking.
* | | Add additional SUSE and openSUSE platforms - micro, hpc (#1753)James Yang2022-08-092-2/+3
| | | | | | | | | | | | | | | * Add additional SUSE and openSUSE platforms - micro, hpc Signed-off-by: jamesongithub@users.noreply.github.com <jamesongithub@users.noreply.github.com>
* | | Bump version to 18.0.18 by Chef Expeditorv18.0.18Chef Expeditor2022-08-093-5/+6
| | | | | | | | | | | | Obvious fix; these changes are the result of automation not creative thinking.
* | | Fix FIPS mode detection (#1754)Stan Hu2022-08-092-3/+4
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Previously FIPS detection relied on the `OpenSSL::OPENSSL_FIPS` constant being defined. However, on RedHat operating systems, this constant is always defined in `/usr/include/openssl/opensslconf-x86_64.h`. As a result, on such operating systems FIPS mode would erroneously be labeled as enabled. This constant is a necessary but not sufficient condition to determine whether FIPS is actually enabled. OpenSSL has a runtime `fips_mode` check (https://wiki.openssl.org/index.php/FIPS_mode()) that should be used instead. Ruby will use this if the `OPENSSL_FIPS` compile-time constant is available: https://github.com/ruby/ruby/blob/685efac05983dee44ce2d96c24f2fcb96a0aebe2/ext/openssl/ossl.c#L413-L428 Signed-off-by: Stan Hu <stanhu@gmail.com>
* | | Bump version to 18.0.17 by Chef Expeditorv18.0.17Chef Expeditor2022-08-023-5/+6
| | | | | | | | | | | | Obvious fix; these changes are the result of automation not creative thinking.
* | | Merge pull request #1758 from balasankarc/fix-constant-reinitialized-warningsJohn McCrae2022-08-024-71/+79
|\ \ \ | |_|/ |/| |
| * | Do not attempt to reinitialize constantsBalasankar 'Balu' C2022-07-214-71/+79
|/ / | | | | | | Signed-off-by: Balasankar 'Balu' C <balu@dravidam.net>
* | Bump version to 18.0.16 by Chef Expeditorv18.0.16Chef Expeditor2022-06-143-5/+6
| | | | | | | | Obvious fix; these changes are the result of automation not creative thinking.
* | Merge pull request #1751 from chef/dependabot/bundler/rubocop-performance-1.14.2John McCrae2022-06-141-1/+1
|\ \
| * | Update rubocop-performance requirement from 1.13.3 to 1.14.2dependabot[bot]2022-06-081-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Updates the requirements on [rubocop-performance](https://github.com/rubocop/rubocop-performance) to permit the latest version. - [Release notes](https://github.com/rubocop/rubocop-performance/releases) - [Changelog](https://github.com/rubocop/rubocop-performance/blob/master/CHANGELOG.md) - [Commits](https://github.com/rubocop/rubocop-performance/compare/v1.13.3...v1.14.2) --- updated-dependencies: - dependency-name: rubocop-performance dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
* | | Bump version to 18.0.15 by Chef Expeditorv18.0.15Chef Expeditor2022-06-143-4/+12
| |/ |/| | | | | Obvious fix; these changes are the result of automation not creative thinking.
* | Merge pull request #1748 from turrisxyz/feat/dependabot-github-actionsJohn McCrae2022-06-141-0/+4
|\ \ | |/ |/|
| * chore: Included githubactions in the dependabot confignaveensrinivasan2022-05-011-0/+4
| | | | | | | | | | | | | | | | | | | | | | This should help with keeping the GitHub actions updated on new releases. This will also help with keeping it secure. Dependabot helps in keeping the supply chain secure https://docs.github.com/en/code-security/dependabot GitHub actions up to date https://docs.github.com/en/code-security/dependabot/working-with-dependabot/keeping-your-actions-up-to-date-with-dependabot https://github.com/ossf/scorecard/blob/main/docs/checks.md#dependency-update-tool Signed-off-by: naveensrinivasan <172697+naveensrinivasan@users.noreply.github.com>
* | Update CHANGELOG.md to reflect the promotion of 18.0.14Chef Expeditor2022-06-061-27/+24
| | | | | | | | Obvious fix; these changes are the result of automation not creative thinking.
* | Bump version to 18.0.14 by Chef Expeditorv18.0.14Chef Expeditor2022-06-023-5/+6
| | | | | | | | Obvious fix; these changes are the result of automation not creative thinking.
* | Merge pull request #1747 from chef/jfm/ohai_ruby3.1John McCrae2022-06-022-8/+9
|\ \
| * | Updated Testing Ruby 3.1 support to get past metadata errorsJohn McCrae2022-04-201-5/+5
| | | | | | | | | | | | Signed-off-by: John McCrae <john.mccrae@progress.com>
| * | Testing Ruby 3.1 supportJohn McCrae2022-04-201-3/+4
| |/ | | | | | | Signed-off-by: John McCrae <john.mccrae@progress.com>
* | Bump version to 18.0.13 by Chef Expeditorv18.0.13Chef Expeditor2022-05-313-5/+6
| | | | | | | | Obvious fix; these changes are the result of automation not creative thinking.
* | Merge pull request #1741 from mattp-/maintpowell-progress2022-05-312-3/+86
|\ \ | | | | | | networking/linux: map src only default routes accordingly
| * | update commentsMatt Phillips2022-05-181-2/+1
| | | | | | | | | | | | Signed-off-by: Matt Phillips <mphillips81@bloomberg.net>
| * | add more verbose comments to new route calculation testsMatt Phillips2022-05-161-4/+20
| | | | | | | | | | | | | | | | | | | | | given the density of whats going on; this hopefully makes things more clear. Signed-off-by: Matt Phillips <mphillips81@bloomberg.net>
| * | prefer route that explicitly define a deviceMatt Phillips2022-05-162-4/+25
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | in theory I don't this should occur in real life, as I'm pretty sure /usr/sbin/ip should always print the dev routes above non dev routes if the metric is the same, but it is a good case to cover in code. also removed the default metric 10 gateway route as it was spurious/irrelevant to the test. Signed-off-by: Matt Phillips <mphillips81@bloomberg.net>
| * | networking/linux: map src only default routes accordinglyMatt Phillips2022-05-162-1/+48
| |/ | | | | | | | | | | | | | | | | | | | | | | in certain configurations a default route can be set via src only / not dev, but should still be accounted for in terms of calculating the 'favored' default route / what is chosen as ipaddress for a given node. This change augments the previously added changes to account for nexthop multipath routing; but only in scenarios src address is set but only in scenarios src address is set. Signed-off-by: Matt Phillips <mphillips81@bloomberg.net>
* | Bump version to 18.0.12 by Chef Expeditorv18.0.12Chef Expeditor2022-05-173-5/+6
| | | | | | | | Obvious fix; these changes are the result of automation not creative thinking.
* | Merge pull request #1740 from chef/dependabot/bundler/rubocop-performance-1.13.3PrajaktaPurohit2022-05-171-1/+1
|\ \ | | | | | | Update rubocop-performance requirement from 1.13.2 to 1.13.3
| * | Update rubocop-performance requirement from 1.13.2 to 1.13.3dependabot[bot]2022-03-071-1/+1
| | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Updates the requirements on [rubocop-performance](https://github.com/rubocop/rubocop-performance) to permit the latest version. - [Release notes](https://github.com/rubocop/rubocop-performance/releases) - [Changelog](https://github.com/rubocop/rubocop-performance/blob/master/CHANGELOG.md) - [Commits](https://github.com/rubocop/rubocop-performance/compare/v1.13.2...v1.13.3) --- updated-dependencies: - dependency-name: rubocop-performance dependency-type: direct:development ... Signed-off-by: dependabot[bot] <support@github.com>
* | | Bump version to 18.0.11 by Chef Expeditorv18.0.11Chef Expeditor2022-05-173-5/+6
| | | | | | | | | | | | Obvious fix; these changes are the result of automation not creative thinking.
* | | Merge pull request #1746 from turrisxyz/naveen/feat/set-perms-actionsPrajaktaPurohit2022-05-172-0/+6
|\ \ \ | |_|/ |/| | Set permissions for GitHub actions
| * | Set permissions for GitHub actionsnaveensrinivasan2022-04-102-0/+6
|/ / | | | | | | | | | | | | | | | | | | | | | | | | | | Restrict the GitHub token permissions only to the required ones; this way, even if the attackers will succeed in compromising your workflow, they won’t be able to do much. - Included permissions for the action. https://github.com/ossf/scorecard/blob/main/docs/checks.md#token-permissions https://docs.github.com/en/actions/using-workflows/workflow-syntax-for-github-actions#permissions https://docs.github.com/en/actions/using-jobs/assigning-permissions-to-jobs [Keeping your GitHub Actions and workflows secure Part 1: Preventing pwn requests](https://securitylab.github.com/research/github-actions-preventing-pwn-requests/) Signed-off-by: naveensrinivasan <172697+naveensrinivasan@users.noreply.github.com>
* | Bump version to 18.0.10 by Chef Expeditorv18.0.10Chef Expeditor2022-04-073-5/+6
| | | | | | | | Obvious fix; these changes are the result of automation not creative thinking.
* | Merge pull request #1744 from chef/jfm/ohai_ruby3.1John McCrae2022-04-0710-11/+20
|\ \
| * | Updating RUBY_PLATFORM on Windows for Ruby 3.1 CompatibilityJohn McCrae2022-04-071-1/+0
| | | | | | | | | | | | Signed-off-by: John McCrae <john.mccrae@progress.com>
| * | Updating for Ruby 3.1John McCrae2022-04-062-2/+5
| | | | | | | | | | | | Signed-off-by: John McCrae <john.mccrae@progress.com>
| * | Updating for Ruby 3.1John McCrae2022-04-061-2/+1
| | | | | | | | | | | | Signed-off-by: John McCrae <john.mccrae@progress.com>
| * | Updating for Ruby 3.1John McCrae2022-04-061-1/+3
| | | | | | | | | | | | Signed-off-by: John McCrae <john.mccrae@progress.com>
View Lorry Controller Status