In the example below the managed-servers plugin is not compatible with other provisioning providers.
not sure if this is just vagrant not allowing you to specify the provider using --provider with a provision request.
My only workaround so far is to uninstall the managed-servers plugin everytime I need to provision to rackspace. Is there a better workaround available?
$ vagrant plugin install vagrant-managed-servers
Installing the 'vagrant-managed-servers' plugin. This can take a few minutes...
Installed the plugin 'vagrant-managed-servers (0.7.1)'!
In the example below the managed-servers plugin is not compatible with other provisioning providers.
not sure if this is just vagrant not allowing you to specify the provider using --provider with a provision request.
My only workaround so far is to uninstall the managed-servers plugin everytime I need to provision to rackspace. Is there a better workaround available?
$ vagrant plugin install vagrant-managed-servers Installing the 'vagrant-managed-servers' plugin. This can take a few minutes... Installed the plugin 'vagrant-managed-servers (0.7.1)'!
$ vagrant plugin list vagrant-cachier (1.2.1) vagrant-host-shell (0.0.4) vagrant-hosts (2.6.1) vagrant-managed-servers (0.7.1) vagrant-rackspace (0.1.10) vagrant-share (1.1.4, system) $ vagrant provision
No host IP was given to the Vagrant core NFS helper. This is an internal error that should be reported as a bug
$ vagrant plugin uninstall vagrant-managed-servers Uninstalling the 'vagrant-managed-servers' plugin...
$vagrant provision ==> pinas01: Rsyncing folder: /Users/PLACES/projects/platforms/rs_hosting/ => /vagrant
I have just tested this out using libvirt and dont see the same issues? is this a bug with vagrant-managed-servers or rackspace. plugin?