Skip to content
New issue

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

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

Already on GitHub? # to your account

updated ohai recipe to work with v4.1.0 of the ohai cookbook #409

Closed
wants to merge 1 commit into from
Closed

Conversation

mjsprojects
Copy link

@mjsprojects mjsprojects commented Jun 1, 2016

Some changes were made in v4.1.0 of the Ohai cookbook that broke Nginx, specifically it was throwing a method not found for the location of the plugin_path.


This change is Reviewable

@lhriley-tm
Copy link

@miketheman Please increase the priority of this pull request.

This is a huge problem for us. We have ohai plugins which rely on the ohai cookbook @4.0.0+. This is now preventing us from deploying new cookbooks which rely on the newer ohai cookbook and also this nginx cookbook.

Thanks!

also: #419

@patcon
Copy link

patcon commented Jul 8, 2016

Odd that this is only getting recent attention, but my infra is unfortunately being held back as well

Any expediting would be appreciated :)

@patcon
Copy link

patcon commented Jul 8, 2016

fwiw, I'm not even using nginx cookbook, so for now, i can just update to 3.0 in my berksfile via git ref.

@aight8
Copy link

aight8 commented Jul 18, 2016

Any update to this PR??

@lhriley-tm
Copy link

Since there hasn't been any movement on this, we've cloned the PR and deployed it. Works fine, but not really happy to do it since we will have to more diligent in monitoring for any future patches to ensure this problem doesn't come up again.

@lmunro
Copy link

lmunro commented Jul 19, 2016

👍 👍 👍 👍 👍 👍 pleaasse help @miketheman

@tas50
Copy link
Contributor

tas50 commented Aug 2, 2016

I'd love to get everyone on the new Ohai cookbook since I wrote that, but doing so removes support for Chef 11, which a lot of users are still one. I've prepped a PR for a final 2.X release of this cookbook that resolves some of the Ohai issues and allows using the 3.X Ohai cookbook. After that in the 3.X version of this cookbook, where only Chef 12+ is supported we can require Ohai 4.X


recipe 'nginx', 'Installs nginx package and sets up configuration with Debian apache style with sites-enabled/sites-available'
recipe 'nginx::source', 'Installs nginx from source and sets up configuration with Debian apache style with sites-enabled/sites-available'

depends 'apt', '~> 2.2'
depends 'bluepill', '~> 2.3'
depends 'build-essential', '~> 2.0'
depends 'ohai', '~> 2.0'
depends 'ohai', '~> 4.1.0'
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Why such strict versioning being used here? Shouldn't ~> 4.0 be enough?

@tas50
Copy link
Contributor

tas50 commented Sep 21, 2016

4.1 would be ideal as it would allow any 4.x cookbook but set the minimum to 4.1

eherot added a commit to evertrue/nginx-cookbook that referenced this pull request Sep 22, 2016
@tas50
Copy link
Contributor

tas50 commented Sep 17, 2017

Thanks for opening this PR. With the merge of the chef_nginx codebase back into the nginx cookbook I believe it’s no longer necessary. I’m going to close this out now, and I hope you can check out the massive changes that landed on master here #435

@tas50 tas50 closed this Sep 17, 2017
@lock
Copy link

lock bot commented Apr 25, 2020

This thread has been automatically locked since there has not been any recent activity after it was closed. Please open a new issue for related bugs.

@lock lock bot locked as resolved and limited conversation to collaborators Apr 25, 2020
# for free to subscribe to this conversation on GitHub. Already have an account? #.
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

8 participants