-
Notifications
You must be signed in to change notification settings - Fork 100
[Chef 12.0] Cannot find a provider for deploy_revision[application] on ubuntu version 12.04 #53
Comments
Can you try with 12.0.1? They fixed some compat issues that might help. |
Tried it with Chef 12.0.1 and I'm getting the same error. |
Same on Ubuntu 14.04:
|
I ran chef with
|
Now paging @danielsdeleo @sersut @lamont-granquist From that error, it certainly sounds like it should be working. |
need the full stacktrace and full debug logs. from the error message it is clearly falling into the old provider platform map stuff and failing, from the debug logs it is clearly succeeding in the provider resolver so should never even get there. without a lot more context it just looks clearly insane and i don't know what to suggest. |
@lamont-granquist here's the full stracktrace |
Ah yeah these lines are the issue: https://github.com/poise/application/blob/master/libraries/default.rb#L141-L145 That should hit this API instead: https://github.com/opscode/chef/blob/master/lib/chef/resource.rb#L682 So something like:
Which should be backcompat with Chef-11, but might need the same arity check if you want to be backcompat with those old versions. We probably need to extract out define_resource+friends from the Recipe DSL to get it away from method_missing and then really have a well-defined public API for building resources and providers like this. |
@lamont-granquist Ahh got it, thanks! |
I can confirm this issue on Ubuntu 14.04 and CentOS 7 as well. Since there is already a stack trace for 14.04, I'll provide the CentOS 7 trace: https://gist.github.com/erulabs/70b4854f0c10f86b19f6 "Cannot find a provider for deploy_revision[STRING] on centos version 7.0.1406" Please let me know if any additional information is required :) Thank you! |
Seeing this as well. |
👍 wondering how to proceed. This is my last blocker on chef 12. |
I was starting to migrate to Chef 12 but then ran into this issue as well |
This is currently blocking my entire deployment. Any idea how I can fix this on my own? |
@andybear use fork with a fix, e.g. in your Berksfile cookbook 'application', git: 'git@github.com:kangguru/application.git', ref: 'f7fc8797d789856a389adbe6f33647e3f5ad4ca9' |
@coderanger Can we help in any way, or get this commit merged in to master? kangguru@f7fc879 |
Yes, will be merging this over and doing a release before I launch in to the upgrade work. |
🎉 🎈 🎂 🎁 |
Got to have the one last "lol legacy" release for people that can't upgrade easily >_< |
Hi @coderanger , just noticed you changed some tests, any news on this issue? We will rollback to chef 11 otherwise :-( |
@jujugrrr Getting regression tests in place before I merge the fix. |
Travis tells me things are happy! https://travis-ci.org/poise/application/builds/47034505 |
Released version 4.1.6 to supermarket. |
You're the best. Thanks! |
cheers! |
application_python has in its metadata.rb This fix wasn't applied to the 3.x cookbook, so application_python is broke on Chef 12 until 85f92b0 is applied to 3.x |
This looks to be related with the changes in Chef 12 regarding recipe DSL and providers.
The text was updated successfully, but these errors were encountered: