vagrant installs plugin without errors, but cant list it

[chuxau]

Hi,

Running Vagrant 1.7.2 here .. on Debian wheezy x64

vagrant plugin install vagrant-triggers runs Ok

$ vagrant plugin install vagrant-triggers --verbose
Installing the 'vagrant-triggers' plugin. This can take a few minutes...
Fetching source index from http://gems.hashicorp.com/
Fetching gem metadata from https://rubygems.org/.........
Fetching additional metadata from https://rubygems.org/..........
Resolving dependencies...
Using builder 3.2.2
Using gyoku 1.2.2
Using mini_portile 0.6.0
Using nokogiri 1.6.3.1
Using akami 1.2.2
Using bundler 1.7.11
Using hitimes 1.2.2
Using timers 4.0.1
Using celluloid 0.16.0
Using ffi 1.9.8
Using childprocess 0.5.6
Using erubis 2.7.0
Using gssapi 1.0.3
Using hashicorp-checkpoint 0.1.4
Using httpclient 2.6.0.1
Using rack 1.6.0
Using httpi 0.9.7
Using i18n 0.6.11
Using json 1.8.2
Using rb-fsevent 0.9.4
Using rb-inotify 0.9.5
Using listen 2.8.4
Using little-plugger 1.1.3
Using log4r 1.1.10
Using multi_json 1.11.0
Using logging 1.8.2
Using mime-types 1.25.1
Using net-ssh 2.9.2
Using net-scp 1.1.2
Using net-sftp 2.1.2
Using nori 1.1.5
Using rb-kqueue 0.2.3
Using rdoc 4.2.0
Using rest-client 1.6.8
Using rubyntlm 0.1.1
Using wasabi 1.0.0
Using savon 0.9.5
Using uuidtools 2.1.5
Using wdm 0.1.0
Using winrm 1.1.3
Using vagrant 1.7.2
Using vagrant-share 1.1.3
Installing vagrant-triggers 0.5.0
Installed the plugin 'vagrant-triggers (0.5.0)'!

But then vagrant plugin list would not display vagrant-triggers as an installed plugin .. and other tools that try to use the plugin fail, because as far as vagrant is concerned the plugin is not installed ..

Is this a vagrant version issue ? What could be the problem here?

[laymonk]

Update: this is a debian issue .. I just tested with same version of vagrant on OSX Mavericks, and it works as expected ..

I will troubleshoot this debian issue some more and come back with some feedback .

thanks

[chuxau]

I have been to trace the problem to an out-of-date ruby library .. and an update has resolved my issue .. closing this now