1. Breaking changes:

Both Ansible provisioners are now capable of automatically setting the compatibility_mode that best fits with the Ansible version in use. You may encounter some compatibility issues when upgrading. If you were using Ansible 2.x and referring to the _ssh-prefixed variables present in the generated inventory (e.g. ansible_ssh_host). In this case, you can fix your Vagrant setup by setting compatibility_mode = "1.8", or by migrating to the new variable names (e.g. ansible_host)

2. Full Changelog: https://github.com/hashicorp/vagrant/blob/master/CHANGELOG.md#200-september-7-2017

• Installed locally and verified correct version
• Create brand new project w/ vagrant init and centos7 box, built fine and ssh'd in with no issues
• Ran an ansible project that uses the ansible provisioner. This project did not require setting the compatibility_mode to 1.8 as mentioned, but users should definitely keep an eye on this.