-
in `lib/fog/sakuracloud/docs/getting_started.md`,
```
Create server
use volume.servers.create with :name, :ServerPlan(Plan id)
```
but, doesn't work correctly with that parameters.
```
irb(main):01…
hylom updated
10 years ago
-
I get the warnings, they have meaning, but this error thats killing me does not. theres nothing in the changelogs or readme as far as I can tell.
```
+ kitchen test
-----> Starting Kitchen (v1.4.0)
…
-
-
This is the backtrace -
```
[human:'src'] vagrant up --provider=libvirt
Bringing machine 'default' up with 'libvirt' provider...
/home/hmehra/.vagrant.d/gems/gems/fog-1.28.0/lib/fog/libvirt/requests/…
-
Any ideas?
```
DOTs-MacBook-Pro:sims moboyle$ rails s
/Users/moboyle/.rvm/gems/ruby-2.2.2/gems/rgeo-0.3.20/lib/rgeo/coord_sys/proj4_c_impl.bundle: [BUG] Segmentation fault at 0x00000000000440
ruby 2.…
-
I am trying to bootstrap a few VMs with wirbelsturm on Centos 6.6 and I am seeing the following logs. Can you please recommend a workaround or way forward?
Thanks,
Chirag
```
[wirbelsturm]$ sudo va…
-
T/O
-
When I run `vagrant up`, I get the following error.
```
$ VAGRANT_LOG=debug vagrant up
INFO global: Vagrant version: 1.6.5
INFO global: Ruby version: 2.0.0
INFO global: RubyGems version: 2.0.14
I…
natea updated
9 years ago
-
```
$ VAGRANT_LOG=debug bundle exec vagrant up --provider=ovirt3
Vagrant appears to be running in a Bundler environment. Your
existing Gemfile will be used. Vagrant will not auto-load any plugins
ins…