Page MenuHomePhabricator

Create a larger newsletter-test instance in labs
Closed, ResolvedPublic

Description

The issue was not in the data on redis (which was a few MB) but rather in other stuff on /srv. /srv on a small instance is only 1.5GB, which means it fills up quite quickly...

Options are:

  • moving to a bigger instance (easiest option, I think?)
  • moving /srv from a seperate partition to be on / (might need some fighting with puppet)

I think the best option is moving to a bigger instance (easiest option, I think?).

This is really sad that we get only 1.5 Gig for /srv in a 15 gig small instance though

Event Timeline

01tonythomas assigned this task to Tinaj1234.
01tonythomas raised the priority of this task from to Needs Triage.
01tonythomas updated the task description. (Show Details)

Agreed to kill the old instance, make a new bigger one and install the extension there
The old machine has no useful data on it.

I hit across this error :\

mwvagrant@newsletter-alpha:/srv/mediawiki-vagrant$ vagrant up
No usable default provider could be found for your system.

Vagrant relies on interactions with 3rd party systems, known as
"providers", to provide Vagrant with resources to run development
environments. Examples are VirtualBox, VMware, Hyper-V.

The easiest solution to this message is to install VirtualBox, which
is available for free on all major platforms.

If you believe you already have a provider available, make sure it
is properly installed and configured. You can see more details about
why a particular provider isn't working by forcing usage with
`vagrant up --provider=PROVIDER`, which should give you a more specific
error message for that particular provider.
mwvagrant@newsletter-alpha:/srv/mediawiki-vagrant$

The instance id is now newsletter-test, and /srv/lxc is empty

No usable default provider could be found for your system.

This usually means that the shell alias of vagrant has not been setup for the current shell. type -a vagrant is expected to return "vagrant is aliased to '/usr/local/bin/mwvagrant'". source /etc/profile.d/alias-vagrant.sh can be used to set the alias in the current shell or the user can log out and log back into the Labs host.

It did work, but now I get this.

mwvagrant@newsletter-test:/srv/mediawiki-vagrant$ vagrant up
Bringing machine 'default' up with 'lxc' provider...
==> default: Box 'Wikimedia/trusty64-puppet-lxc' could not be found. Attempting to find and install...
    default: Box Provider: lxc
    default: Box Version: >= 0
;;;==> default: Loading metadata for box 'Wikimedia/trusty64-puppet-lxc'
    default: URL: https://atlas.hashicorp.com/Wikimedia/trusty64-puppet-lxc
==> default: Adding box 'Wikimedia/trusty64-puppet-lxc' (v0.1) for provider: lxc
    default: Downloading: https://atlas.hashicorp.com/Wikimedia/boxes/trusty64-puppet-lxc/versions/0.1/providers/lxc.box
==> default: Successfully added box 'Wikimedia/trusty64-puppet-lxc' (v0.1) for 'lxc'!
==> default: Importing base box 'Wikimedia/trusty64-puppet-lxc'...
==> default: Checking if box 'Wikimedia/trusty64-puppet-lxc' is up to date...
/srv/vagrant-data/gems/gems/mediawiki-vagrant-0.12.0/lib/mediawiki-vagrant/environment.rb:153:in `match': invalid byte sequence in US-ASCII (ArgumentError)
        from /srv/vagrant-data/gems/gems/mediawiki-vagrant-0.12.0/lib/mediawiki-vagrant/environment.rb:153:in `match'
        from /srv/vagrant-data/gems/gems/mediawiki-vagrant-0.12.0/lib/mediawiki-vagrant/environment.rb:153:in `block in roles_available'
        from /srv/vagrant-data/gems/gems/mediawiki-vagrant-0.12.0/lib/mediawiki-vagrant/environment.rb:153:in `map!'
        from /srv/vagrant-data/gems/gems/mediawiki-vagrant-0.12.0/lib/mediawiki-vagrant/environment.rb:153:in `roles_available'
        from /srv/vagrant-data/gems/gems/mediawiki-vagrant-0.12.0/lib/mediawiki-vagrant/environment.rb:136:in `prune_roles'
        from /srv/vagrant-data/gems/gems/mediawiki-vagrant-0.12.0/lib/mediawiki-vagrant/middleware.rb:12:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builder.rb:116:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `block in run'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/util/busy.rb:19:in `busy'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `run'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/call.rb:53:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/box_check_outdated.rb:68:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /srv/vagrant-data/gems/gems/vagrant-lxc-1.2.1/lib/vagrant-lxc/action/create.rb:33:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /srv/vagrant-data/gems/gems/vagrant-lxc-1.2.1/lib/vagrant-lxc/action/handle_box_metadata.rb:41:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/handle_box.rb:56:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builder.rb:116:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `block in run'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/util/busy.rb:19:in `busy'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `run'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/call.rb:53:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builder.rb:116:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `block in run'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/util/busy.rb:19:in `busy'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `run'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:214:in `action_raw'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:191:in `block in action'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/environment.rb:516:in `lock'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:178:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:178:in `action'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'

I've seen that one too. As I recall it means that there are files in /srv/mediawiki-vagrant and/or /srv/vagrant-data that are not readable by the mwvagrant user. This permission would typically be granted by the files being readable by the wikidev group.

Try fixing permissions with something like:

$ chgrp -R wikidev /srv/mediawiki-vagrant
$ chmod -R g+rwX /srv/mediawiki-vagrant

I recently got a patch merged into ops/puppet.git that should fix the default umask permissions on Labs hosts using role::labs::mediawiki_vagrant that I hope will keep this from happening in the future. It will set the default umask to 0002 instead of 0022 for new logins. This would have the same issues as the setting of the vagrant alias that you encountered above however in that it will only apply to new shells spawned after the role is applied by Puppet.

I am sorry bd808, but the result is still negative :(

mwvagrant@newsletter-test:/srv/mediawiki-vagrant$ chgrp -R wikidev /srv/mediawiki-vagrant
mwvagrant@newsletter-test:/srv/mediawiki-vagrant$ chmod -R g+rwX /srv/mediawiki-vagrant
mwvagrant@newsletter-test:/srv/mediawiki-vagrant$ source /etc/profile.d/alias-vagrant.sh
mwvagrant@newsletter-test:/srv/mediawiki-vagrant$ vagrant up
Bringing machine 'default' up with 'lxc' provider...
==> default: Checking if box 'Wikimedia/trusty64-puppet-lxc' is up to date...
/srv/vagrant-data/gems/gems/mediawiki-vagrant-0.12.0/lib/mediawiki-vagrant/environment.rb:153:in `match': invalid byte sequence in US-ASCII (ArgumentError)
        from /srv/vagrant-data/gems/gems/mediawiki-vagrant-0.12.0/lib/mediawiki-vagrant/environment.rb:153:in `match'
        from /srv/vagrant-data/gems/gems/mediawiki-vagrant-0.12.0/lib/mediawiki-vagrant/environment.rb:153:in `block in roles_available'
        from /srv/vagrant-data/gems/gems/mediawiki-vagrant-0.12.0/lib/mediawiki-vagrant/environment.rb:153:in `map!'
        from /srv/vagrant-data/gems/gems/mediawiki-vagrant-0.12.0/lib/mediawiki-vagrant/environment.rb:153:in `roles_available'
        from /srv/vagrant-data/gems/gems/mediawiki-vagrant-0.12.0/lib/mediawiki-vagrant/environment.rb:136:in `prune_roles'
        from /srv/vagrant-data/gems/gems/mediawiki-vagrant-0.12.0/lib/mediawiki-vagrant/middleware.rb:12:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builder.rb:116:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `block in run'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/util/busy.rb:19:in `busy'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `run'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/call.rb:53:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/box_check_outdated.rb:68:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builder.rb:116:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `block in run'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/util/busy.rb:19:in `busy'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `run'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/call.rb:53:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builder.rb:116:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `block in run'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/util/busy.rb:19:in `busy'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `run'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:214:in `action_raw'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:191:in `block in action'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/environment.rb:516:in `lock'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:178:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:178:in `action'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'
mwvagrant@newsletter-test:/srv/mediawiki-vagrant$

but, I have some update here.!

mwvagrant@newsletter-test:/srv/lxc$ ls -l
total 4
drwxrwx--- 3 root wikidev 4096 Dec 10 17:24 mediawiki-vagrant_default_1449768237714_88436

I added myself to the project and logged in to see if I could figure out what was going on. vagrant status showed a created but halted LXC container. vagrant up tried to start the container but blew up:

$ vagrant status
Current machine states:

default                   stopped (lxc)

The container is currently stopped. Run `vagrant up` to bring it up again.

$ vagrant up
Bringing machine 'default' up with 'lxc' provider...
==> default: Checking if box 'Wikimedia/trusty64-puppet-lxc' is up to date...
==> default: Starting container...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 10.0.3.191:22
    default: SSH username: vagrant
    default: SSH auth method: private key
    default:
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default:
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Forwarding ports...
==> default: 80 => 8080 (adapter eth0)
==> default: 443 => 4430 (adapter eth0)
==> default: Setting hostname...
The following SSH command responded with a non-zero exit status.
Vagrant assumes that this means the command failed!

hostname -f

Stdout from the command:



Stderr from the command:

sudo: /usr/bin/sudo must be owned by uid 0 and have the setuid bit set
^C

This looks to be a fatal corruption of the LXC container (wrong permissions on key files inside the container). The best resolution appeared to be to delete the container and start over. If there was valuable data in the container I would try something more heroic but this instance seems to have never been used successfully yet.

$ vagrant destroy
    default: Are you sure you want to destroy the 'default' VM? [y/N] y
==> default: Clearing any previously set forwarded ports...
==> default: Forcing shutdown of container...
==> default: Destroying VM and associated drives...
==> default: Running cleanup tasks for 'lsb_check' provisioner...
==> default: Running cleanup tasks for 'puppet' provisioner...

$ vagrant up
Bringing machine 'default' up with 'lxc' provider...
==> default: Importing base box 'Wikimedia/trusty64-puppet-lxc'...
==> default: Checking if box 'Wikimedia/trusty64-puppet-lxc' is up to date...
==> default: Starting container...
==> default: Waiting for machine to boot. This may take a few minutes...
    default: SSH address: 10.0.3.84:22
    default: SSH username: vagrant
    default: SSH auth method: private key
    default:
    default: Vagrant insecure key detected. Vagrant will automatically replace
    default: this with a newly generated keypair for better security.
    default:
    default: Inserting generated public key within guest...
    default: Removing insecure key from the guest if it's present...
    default: Key inserted! Disconnecting and reconnecting using new SSH key...
==> default: Machine booted and ready!
==> default: Forwarding ports...
==> default: 80 => 8080 (adapter eth0)
==> default: 443 => 4430 (adapter eth0)
==> default: Setting hostname...
==> default: Exporting NFS shared folders...
==> default: Preparing to edit /etc/exports. Administrator privileges will be required...
nfsd not running
 * Exporting directories for NFS kernel daemon...
   ...done.
 * Starting NFS kernel daemon
   ...done.
==> default: Mounting NFS shared folders...
==> default: Running provisioner: lsb_check...
==> default: Running provisioner: puppet...
==> default: Running Puppet with site.pp...
==> default: stdin: is not a tty

[... snip lots of puppet stuff happening ...]
==> default: Notice: Finished catalog run in 745.87 seconds

$ vagrant status
Current machine states:

default                   running (lxc)

The VM is running. To stop this VM, you can run `vagrant halt` to
shut it down forcefully, or you can run `vagrant suspend` to simply
suspend the virtual machine. In either case, to restart it again,
simply run `vagrant up`.

$ curl -v localhost:8080/
* Hostname was NOT found in DNS cache
*   Trying 127.0.0.1...
* Connected to localhost (127.0.0.1) port 8080 (#0)
> GET / HTTP/1.1
> User-Agent: curl/7.35.0
> Host: localhost:8080
> Accept: */*
>
< HTTP/1.1 301 Moved Permanently
< Date: Fri, 11 Dec 2015 16:52:26 GMT
* Server Apache/2.4.7 (Ubuntu) PHP/5.5.9-1ubuntu4.14 is not blacklisted
< Server: Apache/2.4.7 (Ubuntu) PHP/5.5.9-1ubuntu4.14
< X-Powered-By: HHVM/3.6.5
< X-Content-Type-Options: nosniff
< Cache-control: private, must-revalidate, max-age=0
< Vary: Accept-Encoding,Cookie
< Expires: Thu, 01 Jan 1970 00:00:00 GMT
< Location: http://localhost:8080/wiki/Main_Page
< Last-Modified: Fri, 11 Dec 2015 16:52:26 GMT
< Transfer-Encoding: chunked
< Content-Type: text/html; charset=utf-8
<
* Connection #0 to host localhost left intact

I think you are ready to enable your roles and start setting up the rest of this testing server.

Thank you very much bd808! I just set up the web proxy at https://newsletter-test.wmflabs.org again. But due to some issues with ssh, I haven't been able to do anything else. Will attempt to do something later.

Newsletter extension has also now been enabled. Thanks again.

Just now got this new error:

mwvagrant@newsletter-test:/srv/mediawiki-vagrant$ source /etc/profile.d/alias-vagrant.sh
mwvagrant@newsletter-test:/srv/mediawiki-vagrant$ vagrant up
Bringing machine 'default' up with 'lxc' provider...
==> default: Importing base box 'Wikimedia/trusty64-puppet-lxc'...
==> default: Checking if box 'Wikimedia/trusty64-puppet-lxc' is up to date...
/srv/vagrant-data/gems/gems/mediawiki-vagrant-0.12.0/lib/mediawiki-vagrant/environment.rb:153:in `match': invalid byte sequence in US-ASCII (ArgumentError)
        from /srv/vagrant-data/gems/gems/mediawiki-vagrant-0.12.0/lib/mediawiki-vagrant/environment.rb:153:in `match'
        from /srv/vagrant-data/gems/gems/mediawiki-vagrant-0.12.0/lib/mediawiki-vagrant/environment.rb:153:in `block in roles_available'
        from /srv/vagrant-data/gems/gems/mediawiki-vagrant-0.12.0/lib/mediawiki-vagrant/environment.rb:153:in `map!'
        from /srv/vagrant-data/gems/gems/mediawiki-vagrant-0.12.0/lib/mediawiki-vagrant/environment.rb:153:in `roles_available'
        from /srv/vagrant-data/gems/gems/mediawiki-vagrant-0.12.0/lib/mediawiki-vagrant/environment.rb:136:in `prune_roles'
        from /srv/vagrant-data/gems/gems/mediawiki-vagrant-0.12.0/lib/mediawiki-vagrant/middleware.rb:12:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builder.rb:116:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `block in run'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/util/busy.rb:19:in `busy'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `run'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/call.rb:53:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/box_check_outdated.rb:68:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /srv/vagrant-data/gems/gems/vagrant-lxc-1.2.1/lib/vagrant-lxc/action/create.rb:33:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /srv/vagrant-data/gems/gems/vagrant-lxc-1.2.1/lib/vagrant-lxc/action/handle_box_metadata.rb:41:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/handle_box.rb:56:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:95:in `block in finalize_action'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builder.rb:116:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `block in run'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/util/busy.rb:19:in `busy'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `run'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/call.rb:53:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builtin/config_validate.rb:25:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/warden.rb:34:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/builder.rb:116:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `block in run'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/util/busy.rb:19:in `busy'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/action/runner.rb:66:in `run'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:214:in `action_raw'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:191:in `block in action'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/environment.rb:516:in `lock'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:178:in `call'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/machine.rb:178:in `action'
        from /opt/vagrant/embedded/gems/gems/vagrant-1.7.4/lib/vagrant/batch_action.rb:82:in `block (2 levels) in run'
mwvagrant@newsletter-test:/srv/mediawiki-vagrant$ vagrant list

and http://newsletter-test.wmflabs.org/ is a 502. Please help :(

AFAICT that (T86282) is a different issue in MediaWiki-Vagrant's Puppet. The error quoted by @01tonythomas is about the Ruby gem that is run as part of the vagrant command.

AFAICT that (T86282) is a different issue in MediaWiki-Vagrant's Puppet. The error quoted by @01tonythomas is about the Ruby gem that is run as part of the vagrant command.

I debugged with @01tonythomas on irc and we eventually figured out that his shell environment was missing the needed alias for vagrant to make it run as the expected user. The ruby errors he got are apparently a variation on the errors described at https://wikitech.wikimedia.org/wiki/Help:MediaWiki-Vagrant_in_Labs#.22No_usable_default_provider_could_be_found_for_your_system..22