Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Handle situations where /proc/cpuinfo lacks core data #1038

Merged
merged 2 commits into from
Aug 22, 2017
Merged

Handle situations where /proc/cpuinfo lacks core data #1038

merged 2 commits into from
Aug 22, 2017

Conversation

tas50
Copy link
Contributor

@tas50 tas50 commented Jul 31, 2017

This works around failures to collect core data on SLES <= 12 SP1. We need to support SLES and core counts are used in several of our product cookbooks.

Signed-off-by: Tim Smith tsmith@chef.io

This works around failures to collect core data on SLES <= 12 SP1. We need to support SLES and core counts are used in several of our product cookbooks.

Signed-off-by: Tim Smith <tsmith@chef.io>
@tas50
Copy link
Contributor Author

tas50 commented Aug 15, 2017

So I should add that this is technically a breaking change. When we ran on older systems previously we delivered completely bogus CPU info. Our tests even accounted for that. Now if we don't have count information we omit it vs. setting it to 0. The hope here is though that we run on these systems (like SLES) and fall back to lscpu, but if lscpu isn't there you're getting a missing value now. I think that's the right thing to do vs. falling back to 0s.

@tas50 tas50 changed the title WIP: Handle situations where /proc/cpuinfo lacks core data Handle situations where /proc/cpuinfo lacks core data Aug 15, 2017
Signed-off-by: Tim Smith <tsmith@chef.io>
@tas50 tas50 merged commit 4816b15 into master Aug 22, 2017
@tas50 tas50 deleted the sles branch August 22, 2017 16:54
@chef chef locked and limited conversation to collaborators Feb 14, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants