You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Running vagrant up with ansible provisioning fails, due to the hosts file not being altered yet. Running vagrant up --provision-with=shell shows the hosts file being updated after the provisioning call.
Expected behaviour
Hostsupdater should execute its hooks prior to provisioning executing.
The text was updated successfully, but these errors were encountered:
I've found that doing a vagrant halt followed by vagrant up works for me, and then I can run vagrant provision as normal, but this isn't ideal. Would be great to see this fixed!
yes, that would be because vagrant halt followed by vagrant up would not trigger provisioning, which you then trigger manually after the fact with vagrant provision :)
Bug Description
Running
vagrant up
withansible
provisioning fails, due to the hosts file not being altered yet. Runningvagrant up --provision-with=shell
shows the hosts file being updated after the provisioning call.Expected behaviour
Hostsupdater should execute its hooks prior to provisioning executing.
The text was updated successfully, but these errors were encountered: