Vagrant 1.6 changed the order of steps Vagrant performs on initialization: it now evaluates the project's Vagrantfile after loading plugins and parsing command-line arguments. This means that the various subcommands provide for role management no longer work, since the relevant plugins are loaded from the top of Vagrantfile, which is now too late a stage to be loading plugins.
Loading plugins from Vagrantfile was always a bit of a hack, but it was a good hack that allowed us to bridge over a complicated plugin packaging process and provide a tailored Vagrant experience right from 'vagrant up'.
I'd like to fix this without adding steps to the installation process, but I'm not sure how. I spent a few hours bashing my head against this problem earlier today and didn't get anywhere. I would really welcome a creative solution.
The relevant bug is https://bugzilla.wikimedia.org/show_bug.cgi?id=65066 , originally reported by Robert Vogel.
Ori
On Sat, May 10, 2014 at 11:48 AM, Ori Livneh ori@wikimedia.org wrote:
Vagrant 1.6 changed the order of steps Vagrant performs on initialization: it now evaluates the project's Vagrantfile after loading plugins and parsing command-line arguments. This means that the various subcommands provide for role management no longer work, since the relevant plugins are loaded from the top of Vagrantfile, which is now too late a stage to be loading plugins.
We're not the only ones whose Vagrant setup broke as a result of this change. An hour ago Vagrant's lead developer said "I'll think about this and see if we can bring this back." < https://github.com/mitchellh/vagrant/issues/3775#issuecomment-42980896%3E. So I'll wait a bit longer before trying out alternative approaches. In the meantime, please stick to 1.5.x.
wikitech-l@lists.wikimedia.org