Last modified: 2014-04-16 06:40:14 UTC
This is indeed a duplicate of bug 61285 (more or less). But wait.. there is more. I'm not sure if I should reopen that one or write here. But I will write the bugreport. I've studied 61285 a bit, and to summarize, the fix in Gerrit change #113988 was the following in puppet/modules/browsertests/manifests/init.pp:80 -cwd => '/srv/browsertests', +cwd => '/srv/browsertests/tests/browser', I've used mediawiki-vagrant commit 875f18f77b5d95be5168a142758178d06a33a6bc and bumped into the same problem described in bug 61285. After trying to manually run the command that puppet was failing on, I've got this: vagrant@mediawiki-vagrant:/srv/browsertests/tests/browser$ bundle install --path /home/vagrant/.gem /usr/lib/ruby/1.9.1/fileutils.rb:247:in `mkdir': Permission denied - /home/vagrant/.gem/ruby (Errno::EACCES) [...] Apparently something set the permission of /home/vagrant/.gem to root:root vagrant@mediawiki-vagrant:/srv/browsertests/tests/browser$ ls -la ~/ [...] drwxr-xr-x 2 root root 4096 Apr 5 21:24 .gem [...] After changing the permission of /home/vagrant/.gem to vagrant:vagrant, the bundle command ran succesfuly, and after that I ran vagrant provision and everything went well. Maybe this could be incorporated in the puppet manifest ?
*** This bug has been marked as a duplicate of bug 61285 ***
