ggiamarchi / vagrant-openstack-provider

Use Vagrant to manage OpenStack Cloud instances.
MIT License
247 stars 101 forks source link

Errors getting network infrmation from VMWare OpenStack Octa #372

Open FilBot3 opened 6 years ago

FilBot3 commented 6 years ago

Using openstack-vagrant-provider version 0.13.0, I am attempting to stand up infrastructure in a VMWare OpenStack Octa Environment. I am using Rake and Ruby's ENV to set my environment variables, but I seem to be running into issues with the provider getting the network information. See link for details.

The Rake task looks like this

namespace :vagrant do
  namespace :os do
    desc 'Run Vagrant commands using the set variables.'
    task :cmd, [:command] do |_t, args|
      ENV['VAGRANT_OPENSTACK_LOG'] = 'debug'
      sh %(
        vagrant #{args.command}
      )
    end
  end
end

I run into the same errors with gathering network information running

rake vagrant:os:cmd["openstack network-list"]

from. I have another Rake task file in my rakelib/ that sets all my ENV variables everytime I run the commands.

joe4dev commented 5 years ago

confirm this issue. It appears that something in/around lib/vagrant-openstack-provider/client/neutron.rb:39:in `get_networks' is broken for the current API version It seems that PR #343 addresses this issue.

This basically disables the ability to launch new instances if more than one network exists in this context.