Last modified: 2014-11-17 21:35:59 UTC

Wikimedia Bugzilla is closed!

Wikimedia migrated from Bugzilla to Phabricator. Bug reports are handled in Wikimedia Phabricator.
This static website is read-only and for historical purposes. It is not possible to log in and except for displaying bug reports and their history, links might be broken. See T63456, the corresponding Phabricator task for complete and up-to-date bug report information.
Bug 61456 - vagrant enable-role followed by vagrant up should trigger a puppet run
vagrant enable-role followed by vagrant up should trigger a puppet run
Status: NEW
Product: MediaWiki-Vagrant
Classification: Unclassified
General (Other open bugs)
unspecified
All All
: Unprioritized normal
: ---
Assigned To: Nobody - You can work on this!
:
Depends on:
Blocks:
  Show dependency treegraph
 
Reported: 2014-02-17 08:30 UTC by Ori Livneh
Modified: 2014-11-17 21:35 UTC (History)
2 users (show)

See Also:
Web browser: ---
Mobile Platform: ---
Assignee Huggle Beta Tester: ---


Attachments

Description Ori Livneh 2014-02-17 08:30:58 UTC
Because not everyone is as awesome as we are about writing idempotent Puppet code, vagrant assumes Puppet runs are an expensive affairs, and it pities the user:

  [default] VM already provisioned. Run `vagrant provision` or use `--provision` to force it

This behavior was added fairly recently. If the user just ran vagrant enable-role, the behavior is bogus: MediaWiki-Vagrant ought to know that the user needs a Puppet run to make the machine consistent with its roster of enabled roles.
Comment 1 Ori Livneh 2014-05-27 10:18:55 UTC
This is now possible by configuring the Puppet provisioner to :run => 'always'.

See https://docs.vagrantup.com/v2/provisioning/basic_usage.html, section "Run once or always".

Not doing it yet since it's not backwards-compatible.
Comment 2 Bryan Davis 2014-11-17 21:35:59 UTC
Bulk unassigning bugs from Ori.

Note You need to log in before you can comment on or make changes to this bug.


Navigation
Links