search

pradels / vagrant-ovirt

Vagrant provider for oVirt and RHEV.
MIT License
36 stars 20 forks source link

uninitialized constant error when using vagrant up #2

Open econchick opened 11 years ago

econchick commented 11 years ago

Using Mac OS X 10.8.3 locally, Red Hat's internal data centers on RHEVM 3.1.0-50.el6ev

$ vagrant plugin install vagrant-ovirt
$ vagrant box add ovirt https://raw.github.com/pradels/vagrant-ovirt/master/example_box/ovirt.box
$ vagrant init
# edited Vagrantfile
$ vagrant up --provider=ovirt

then got this error message:

Bringing machine 'test_vm' up with 'ovirt' provider...
[test_vm] An error occured. Recovering..
[test_vm] VM is not created. Please run `vagrant up` first.
/Users/lynnroot/.vagrant.d/gems/gems/vagrant-ovirt-0.0.1/lib/vagrant-ovirt/action/create_vm.rb:50:in `call': uninitialized constant VagrantPlugins::OVirtProvider::Action::CreateVM::Error (NameError)
    from /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/warden.rb:34:in `call'
    from /Users/lynnroot/.vagrant.d/gems/gems/vagrant-ovirt-0.0.1/lib/vagrant-ovirt/action/set_name_of_domain.rb:24:in `call'
    from /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/warden.rb:34:in `call'
    from /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/runner.rb:61:in `block in run'
    from /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/util/busy.rb:19:in `busy'
    from /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/runner.rb:61:in `run'
    from /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/builtin/call.rb:51:in `call'
    from /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/warden.rb:34:in `call'
    from /Users/lynnroot/.vagrant.d/gems/gems/vagrant-ovirt-0.0.1/lib/vagrant-ovirt/action/connect_ovirt.rb:67:in `call'
    from /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/warden.rb:34:in `call'
    from /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
    from /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/warden.rb:34:in `call'
    from /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/builder.rb:116:in `call'
    from /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/runner.rb:61:in `block in run'
    from /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/util/busy.rb:19:in `busy'
    from /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/action/runner.rb:61:in `run'
    from /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/machine.rb:147:in `action'
    from /Applications/Vagrant/embedded/gems/gems/vagrant-1.2.2/lib/vagrant/batch_action.rb:63:in `block (2 levels) in run'

Any suggestions?

mahesh3267 commented 11 years ago

Hi All,

Even iam also getting the following error when i execute vagrant up --provider=ovirt.

Bringing machine 'test_vm' up with 'ovirt' provider... [test_vm] An error occured. Recovering.. [test_vm] VM is not created. Please run vagrant up first. /root/.vagrant.d/gems/gems/vagrant-ovirt-0.0.2/lib/vagrant-ovirt/action/create_vm.rb:48:in call': undefined methodall' for []:Array (NoMethodError) from /opt/vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/warden.rb:34:in call' from /root/.vagrant.d/gems/gems/vagrant-ovirt-0.0.2/lib/vagrant-ovirt/action/set_name_of_domain.rb:24:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/warden.rb:34:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/runner.rb:61:inblock in run' from /opt/vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/util/busy.rb:19:in busy' from /opt/vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/runner.rb:61:inrun' from /opt/vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/builtin/call.rb:51:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/warden.rb:34:incall' from /root/.vagrant.d/gems/gems/vagrant-ovirt-0.0.2/lib/vagrant-ovirt/action/connect_ovirt.rb:67:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/warden.rb:34:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/builtin/config_validate.rb:25:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/warden.rb:34:incall' from /opt/vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/builder.rb:116:in call' from /opt/vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/runner.rb:61:inblock in run' from /opt/vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/util/busy.rb:19:in busy' from /opt/vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/action/runner.rb:61:inrun' from /opt/vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/machine.rb:147:in action' from /opt/vagrant/embedded/gems/gems/vagrant-1.2.4/lib/vagrant/batch_action.rb:63:inblock (2 levels) in run'

Please let us know if we have any fix for this issue.

myoung34 commented 10 years ago

I've taken over the upstream work. This and new issues should be opened at my fork