Bug ID: 63323
           Summary: `sudo labs-vagrant provision` gets "Permission denied"
                    creating extension repo
           Product: MediaWiki-Vagrant
           Version: unspecified
          Hardware: All
                OS: All
            Status: NEW
          Severity: normal
          Priority: Unprioritized
         Component: General
       Web browser: ---
   Mobile Platform: ---

On a new labs-vagrant instance ee-flow-extra.eqiad.wmflabs

  $ sudo labs-vagrant enable-role flow
works, but

  $ sudo labs-vagrant provision
fails with

  info: mount[files]: allowing mediawiki-vagrant access
notice: /Stage[main]/Mysql/File[/home/vagrant/.my.cnf]/owner: owner changed
'vagrant' to 'vagrant'
clone mediawiki/extensions/Flow]/returns: fatal: could not create work tree dir
'/vagrant/mediawiki/extensions/Flow'.: Permission denied
clone mediawiki/extensions/Flow]/returns: change from notrun to 0 failed: git
clone --recursive --branch master
/vagrant/mediawiki/extensions/Flow returned 128 instead of one of [0] at

But I'm running the command as root, and
vagrant/puppet/modules/git/manifests/clone.pp tries to run as  $user = vagrant.
I don't understand why this unable to clone in a directory owned by vagrant.
  drwxr-xr-x 9 vagrant www-data 4096 Mar 31 18:48

I find just touching a file in here doesn't work,
  spage$ sudo su vagrant
  $ touch /vagrant/mediawiki/extensions/foo
failed.  So maybe there is a sudo or security issue?

Yuvi comments "someone else had issues running commands as other users (with
postgres, I think)... seems labs-related". His workaround
  $ sudo su
  $ labs-vagrant provision
worked, and I added it to

Bug 61397 "allow `sudo -u vagrant <command>` on labs-vagrant" is related.

You are receiving this mail because:
You are on the CC list for the bug.
Wikibugs-l mailing list

Reply via email to