1
votes

When trying to 'vmc push hello' the sinatra sample app as a test of deployment I get:

Time of crash:  
Sun Dec 02 14:11:52 -0800 2012  

NoMethodError: undefined method `[]' for nil:NilClass  

manifests-vmc-plugin-0.4.14/lib/manifests-vmc-plugin.rb:76:in `app_by_tag'  
manifests-vmc-plugin-0.4.14/lib/manifests-vmc-plugin.rb:81:in `find_apps'  
manifests-vmc-plugin-0.4.14/lib/manifests-vmc-plugin/plugin.rb:102  
mothership-0.3.0/lib/mothership/command.rb:78:in `instance_exec'  
mothership-0.3.0/lib/mothership/command.rb:78:in `invoke'  
mothership-0.3.0/lib/mothership/command.rb:82:in `instance_exec'  
mothership-0.3.0/lib/mothership/command.rb:82:in `invoke'  
mothership-0.3.0/lib/mothership/base.rb:50:in `execute'
vmc-0.4.2/lib/vmc/cli.rb:106:in `execute'
mothership-0.3.0/lib/mothership.rb:42:in `start'
vmc-0.4.2/bin/vmc:11
/usr/bin/vmc:19:in `load'
/usr/bin/vmc:19  

This happens when trying to deploy using vmc to 'api.cloudfoundry.com' and micro cloud using the commands 'vmc push hello' and 'vmc push'

4

4 Answers

2
votes

There is an issue with the manifests-vmc-plugin (0.4.14), you can do one of a couple of a few things;

  • Use the legacy version of VMC (3.2.23)
  • Uninstall VMC 0.4.2 and manifests-vmc-plugin 0.4.14 if you already had vmc 0.4.1 and manifests-vmc-plugin 0.4.13 installed.

If you uninstall all versions of VMC and manifests-vmc-plugin, you can re-install vmc 0.4.1, then uninstall manifests-vmc-plugin 0.4.14 and re-install manifests-vmc-plugin 0.4.13 this should leave with a working version of the "new" vmc as apposed the older legacy version.

Hope that all makes sense. I should also add that this issue will be picked up and hopefully resolved in the next 24hrs.

1
votes

Can you downgrade vmc gem version to the previous one? sudo gem uninstall vmc and to be safe sudo gem install vmc [working_version]

1
votes

Running gem update vmc fixed the problem for me. Updates to => manifests-vmc-plugin-0.4.17

0
votes

Make sure you're in the right directory when doing your push.

As a workaround, and to validate that this crash indeed comes from an app detection failure (as the stacktrace seems to imply), you can use vmc push --path <directory of your app contents>