[Chef 12.0] Cannot find a provider for deploy_revision[application] on ubuntu version 12.04 about application HOT 26 CLOSED

Can you try with 12.0.1? They fixed some compat issues that might help.

from application.

Tried it with Chef 12.0.1 and I'm getting the same error.

from application.

Same on Ubuntu 14.04:

ArgumentError
-------------
Cannot find a provider for deploy_revision[portal_api] on ubuntu version 14.04


Cookbook Trace:
---------------
/tmp/vagrant-chef-2/chef-solo-1/cookbooks/application/libraries/default.rb:144:in `deploy_provider'

/tmp/vagrant-chef-2/chef-solo-1/cookbooks/application/libraries/default.rb:152:in `release_path'

/tmp/vagrant-chef-2/chef-solo-1/cookbooks/application/resources/default.rb:94:in `release_path'

/tmp/vagrant-chef-2/chef-solo-1/cookbooks/application/libraries/default.rb:75:in `method_missing'
/tmp/vagrant-chef-2/chef-solo-1/cookbooks/application_ruby/providers/rails.rb:77:in `block in class_from_file'
/tmp/vagrant-chef-2/chef-solo-1/cookbooks/application/providers/default.rb:179:in `block in run_actions_with_context'
/tmp/vagrant-chef-2/chef-solo-1/cookbooks/application/providers/default.rb:176:in `each'
/tmp/vagrant-chef-2/chef-solo-1/cookbooks/application/providers/default.rb:176:in `run_actions_with_context'
/tmp/vagrant-chef-2/chef-solo-1/cookbooks/application/providers/default.rb:161:in `block (2 levels) in run_deploy'

from application.

I ran chef with -l debug and found these lines that might be worth sharing:

* deploy_revision[nodejs application] action deploy[2014-12-10T20:31:45+00:00] INFO: Processing deploy_revision[nodejs application] action deploy (/tmp/kitchen/cache/cookbooks/application/providers/default.rb line 123)       
       [2014-12-10T20:31:45+00:00] DEBUG: providers for generic deploy_revision resource enabled on node include: [Chef::Provider::Deploy::Revision]

[2014-12-10T20:31:45+00:00] DEBUG: providers that refused resource deploy_revision[nodejs application] were: []       
[2014-12-10T20:31:45+00:00] DEBUG: providers that support resource deploy_revision[nodejs application] include: [Chef::Provider::Deploy::Revision]       
[2014-12-10T20:31:45+00:00] DEBUG: providers that survived replacement include: [Chef::Provider::Deploy::Revision]       
       [2014-12-10T20:31:45+00:00] DEBUG: deploy_revision[nodejs application] finding current git revision

from application.

Now paging @danielsdeleo @sersut @lamont-granquist

From that error, it certainly sounds like it should be working.

from application.

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.

from application.

@lamont-granquist here's the full stracktrace

https://gist.github.com/marcoamorales/da98e69aef2d86175ab4

from application.

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:

@deploy_resource.provider_for_action(:nothing)

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.

from application.

@lamont-granquist Ahh got it, thanks!

from application.

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!

from application.

Seeing this as well.
Is a fix likely to be forthcoming, or am i better off forking and hacking my dependency chain?

from application.

👍 wondering how to proceed. This is my last blocker on chef 12.

from application.

I was starting to migrate to Chef 12 but then ran into this issue as well

from application.

This is currently blocking my entire deployment. Any idea how I can fix this on my own?

from application.

@andybear use fork with a fix, e.g. in your Berksfile

cookbook 'application', git: '[email protected]:kangguru/application.git', ref: 'f7fc8797d789856a389adbe6f33647e3f5ad4ca9'

from application.

@coderanger Can we help in any way, or get this commit merged in to master? kangguru@f7fc879

from application.

Yes, will be merging this over and doing a release before I launch in to the upgrade work.

from application.

🎉 🎈 🎂 🎁

from application.

Got to have the one last "lol legacy" release for people that can't upgrade easily >_<

from application.

Hi @coderanger , just noticed you changed some tests, any news on this issue? We will rollback to chef 11 otherwise :-(

from application.

@jujugrrr Getting regression tests in place before I merge the fix.

from application.

Travis tells me things are happy! https://travis-ci.org/poise/application/builds/47034505

from application.

Released version 4.1.6 to supermarket.

from application.

You're the best. Thanks!

from application.

cheers!

from application.

application_python has in its metadata.rb
depends "application", "~> 3.0"

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

from application.