aurora-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Bill Farner <>
Subject Heads up - please destroy and re-create your vagrant environment
Date Tue, 17 Mar 2015 02:32:42 GMT
I just committed a change that alters the scheduler command line arguments
in the upstart configuration.  Due to the way vagrant provisioning
currently works, this means the now-removed argument will be unrecognized
by new scheduler builds.  Please use vagrant destroy to nuke this old

I plan to improve this situation with AURORA-1204 [1] so the upstart
configurations are updated when code is synced in the vagrant environment.
Additionally, i have created AURORA-1203 [2] to track an idea to make it
much cheaper to destroy and re-create the vagrant environment.



  • Unnamed multipart/alternative (inline, None, 0 bytes)
View raw message