-
Notifications
You must be signed in to change notification settings - Fork 102
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
run_provisioner': Catched Error #240
Comments
This is definitely bug introduced in 0.7.0. I don't see this error when running on 0.6.1. Here what I get:
|
Idem
|
FYI: is a workaround for this issue. |
Sharpie
added a commit
to Sharpie/vagrant-openstack-provider
that referenced
this issue
Nov 1, 2015
Vagrant core tries very hard to be lazy and only loads plugin classes when necessary. This caused a break in version 0.7.0 when a test was added to the `provision` action to check if an object is of class `VagrantPlugins::Shell::Provisioner`. The `vagrant up` action triggers a lazy load of this class, while the `vagrant provsion` action does not. This patch ensures the provisioner class is loaded by retrieving it through the Vagrant plugin manager instead of using a direct reference. Fixes ggiamarchi#240
Submitted PR #253 which should fix this. |
Sharpie
added a commit
to Sharpie/vagrant-openstack-provider
that referenced
this issue
Nov 1, 2015
Vagrant core tries very hard to be lazy and only loads plugin classes when necessary. This caused a break in version 0.7.0 when a test was added to the `provision` action to check if an object is of class `VagrantPlugins::Shell::Provisioner`. The `vagrant up` action triggers a lazy load of this class, while the `vagrant provsion` action does not. This patch ensures the provisioner class is loaded by retrieving it through the Vagrant plugin manager instead of using a direct reference. Fixes ggiamarchi#240
Sharpie
added a commit
to Sharpie/vagrant-openstack-provider
that referenced
this issue
Nov 1, 2015
Vagrant core tries very hard to be lazy and only loads plugin classes when necessary. This caused a break in version 0.7.0 when a test was added to the `provision` action to check if an object is of class `VagrantPlugins::Shell::Provisioner`. The `vagrant up` action triggers a lazy load of this class, while the `vagrant provsion` action does not. This patch ensures the provisioner class is loaded by retrieving it through the Vagrant plugin manager instead of using a direct reference. Fixes ggiamarchi#240
Sharpie
added a commit
to Sharpie/vagrant-openstack-provider
that referenced
this issue
Jan 18, 2016
Vagrant core tries very hard to be lazy and only loads plugin classes when necessary. This caused a break in version 0.7.0 when a test was added to the `provision` action to check if an object is of class `VagrantPlugins::Shell::Provisioner`. The `vagrant up` action triggers a lazy load of this class, while the `vagrant provsion` action does not. This patch ensures the provisioner class is loaded by retrieving it through the Vagrant plugin manager instead of using a direct reference. Fixes ggiamarchi#240
Sharpie
added a commit
to Sharpie/vagrant-openstack-provider
that referenced
this issue
Jul 31, 2016
Vagrant core tries very hard to be lazy and only loads plugin classes when necessary. This caused a break in version 0.7.0 when a test was added to the `provision` action to check if an object is of class `VagrantPlugins::Shell::Provisioner`. The `vagrant up` action triggers a lazy load of this class, while the `vagrant provsion` action does not. This patch ensures the provisioner class is loaded by retrieving it through the Vagrant plugin manager instead of using a direct reference. Fixes ggiamarchi#240
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Getting an error at the provisioner part :
/home/anton/.vagrant.d/gems/gems/vagrant-openstack-provider-0.7.0/lib/vagrant-openstack-provider/action/provision.rb:34:in `run_provisioner': Catched Error: Catched Error: uninitialized constant VagrantPlugins::Shell::Provisioner (NameError)
cat Vagrantfile
The text was updated successfully, but these errors were encountered: