[01:59:21] tgr: your docroot stuff makes a lot of noise on windows hosts -- Error: /Stage[main]/Apache/File[/vagrant/srv/docroot/w/COPYING]/ensure: change from absent to link failed: Could not set 'link' on ensure: Protocol error - (/vagrant/mediawiki/COPYING, /vagrant/srv/docroot/w/COPYING) [02:01:17] that's strande, why would it try to make symlinks? [02:03:44] hm, /var/www/w/ does have a bunch of symlinks [02:12:05] bd808: puppet doc says windows provider can manage symlinks [02:12:22] so maybe some sort of permission issue? [02:12:32] the pastebin I'm reading seems to say otherwise [02:12:41] http://pastebin.com/9EL0T0sq [02:13:10] the real problem for this GCI kid is the git pack corruption thing [02:14:35] https://docs.puppet.com/puppet/4.8/resources_file_windows.html#make-sure-puppets-user-account-has-appropriate-permissions [02:15:26] did you see my workaround comment on the pack bug? [02:16:08] btw I reran the git clone command (without vagrant) a few hours ago and it worked [02:16:39] so it's either random or somehow specific to how git connects from a vagrant box (which seems unlikely) [02:17:31] I think it has something to do with the git version on mw-vagrant, http, and the state of the gerrit origin repos [02:17:52] I'm poking c.had about it in another channel [02:18:09] re: https://gerrit.wikimedia.org/r/#/c/187874/6/puppet/modules/apache/manifests/init.pp they can try recurse => true instead of recurse => remote, docs say it has the same result but different mechanism so maybe it helps [02:18:12] I've jsut repoduced 3 times in a row [02:18:18] but I would look at permissions first [02:19:41] well, using ssh worked for me when I had that error, they should try that [04:55:19] tgr: when you get a chance, test out https://gerrit.wikimedia.org/r/#/c/328335/ and see if it works around the failing git clone problem. (totally untested by me at the moment other than with manual git clones inside the VM)