initialize': must pass :url (ArgumentError) when neutron url is not present

[ftfniqpl]

hi :
I used Openstack version is havana, hypervisor is a docker, vagrant version is 1.6.5
Vagrantfile file configuration is:

require 'vagrant-openstack-provider'
Vagrant.configure('2') do |config|
  config.vm.box       = 'dummy-openstack'
  config.vm.box_url   = 'https://github.com/ggiamarchi/vagrant-openstack/raw/master/source/dummy.box'

  config.ssh.username = 'stack'

  config.vm.provider :openstack do |os|
    os.openstack_auth_url = 'http://192.168.20.206:35357/v2.0/tokens'
    os.username           = 'admin'
    os.password           = 'password'
    os.tenant_name        = 'admin'
    os.flavor             = 'm1.docker'
    os.image              = 'docker_paas'
    os.floating_ip_pool   = ''
  end
end

When I use vagrant up --provider = openstack and the error message is:

/opt/vagrant/embedded/gems/gems/rest-client-1.6.8/lib/restclient/request.rb:45:in `initialize': must pass :url (ArgumentError)
    from /opt/vagrant/embedded/gems/gems/rest-client-1.6.8/lib/restclient/request.rb:35:in `new'
    from /opt/vagrant/embedded/gems/gems/rest-client-1.6.8/lib/restclient/request.rb:35:in `execute'
    from /opt/vagrant/embedded/gems/gems/rest-client-1.6.8/lib/restclient.rb:70:in `get'
    from /root/.vagrant.d/gems/gems/vagrant-openstack-provider-0.4.0/lib/vagrant-openstack-provider/client/neutron.rb:21:in `get_api_version_list'
    from /root/.vagrant.d/gems/gems/vagrant-openstack-provider-0.4.0/lib/vagrant-openstack-provider/action/connect_openstack.rb:53:in `read_network_api_version'
    from /root/.vagrant.d/gems/gems/vagrant-openstack-provider-0.4.0/lib/vagrant-openstack-provider/action/connect_openstack.rb:48:in `read_endpoint_catalog'
    from /root/.vagrant.d/gems/gems/vagrant-openstack-provider-0.4.0/lib/vagrant-openstack-provider/action/connect_openstack.rb:24:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/warden.rb:34:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/builder.rb:116:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/runner.rb:66:in `block in run'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/util/busy.rb:19:in `busy'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/action/runner.rb:66:in `run'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/machine.rb:196:in `action_raw'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/machine.rb:173:in `block in action'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/environment.rb:474:in `lock'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/machine.rb:161:in `call'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/machine.rb:161:in `action'
    from /opt/vagrant/embedded/gems/gems/vagrant-1.6.5/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'

[ggiamarchi]

The bug comes from the fact that the plugin did not manage to resolve Neutron endpoint URL from Keystone catalog. Either, Neutron service is not declared in you catalog or there is a bug in the plugin. Can you provide us the full log of your error by setting the environment variable VAGRANT_OPENSTACK_LOG to debug and re-run the up command

export VAGRANT_OPENSTACK_LOG=debug
vagrant up --provider=openstack

In the other hand, with your Vagrantfile, the plugin does not need to call Neutron, thus the plugin should not fail if it is not available. This is fixed in release 0.4.1. You can upgrade with command :

vagrant plugin update vagrant-openstack-provider

Last thing (not related to the bug), in your Vagrantfile os.floating_ip_pool = '' is not correct. Either floating_ip_pool or floating_ip must be provided with a good value. You can run vagrant openstack floatingip-list to get the name of you floating ip pool.