vagrant-openstack-provider icon indicating copy to clipboard operation
vagrant-openstack-provider copied to clipboard

Errors getting network infrmation from VMWare OpenStack Octa

Open FilBot3 opened this issue 6 years ago • 1 comments

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.

  • https://gist.github.com/predatorian3/0fe24b218197c826dabe2fa906b7482d#file-vagrant-openstack-provider_errors_00-log-L63-L74

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.

FilBot3 avatar Sep 17 '18 15:09 FilBot3

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.

joe4dev avatar Dec 19 '18 14:12 joe4dev