Conflicting IP address issue

[pf-nate-bennett]

So after configuring it to utilize a VPC for multi-node, I fail on this error with zk1. When I vagrant destroy it removes the instance wit the offending IP. Then brings zk1 back up with that same IP. Then I get the same error.

vagrant up --provider=aws --no-parallel
using vagrant-berkshelf
using vagrant-omnibus
using vagrant-hosts
Bringing machine 'zk1' up with 'aws' provider...
Bringing machine 'master1' up with 'aws' provider...
Bringing machine 'master2' up with 'aws' provider...
Bringing machine 'slave1' up with 'aws' provider...
Bringing machine 'slave2' up with 'aws' provider...
Bringing machine 'marathon' up with 'aws' provider...
[snip]
==> master1: Using chef_handler (1.2.0)
==> master1: Using docker (0.40.3) from git://github.com/bflad/chef-docker.git (at master)
==> master1: Using java (1.31.0)
==> master1: Using mesos (0.2.2) from git://github.com/everpeace/cookbook-mesos.git (at master)
==> master1: Using maven (1.3.0)
==> master1: Using python (1.4.6)
==> master1: Using windows (1.37.0)
==> master1: Using ulimit (0.3.3)
==> master1: Using yum-epel (0.6.2)
==> master1: Using yum (3.6.3)
==> master1: Vendoring 7-zip (1.0.2) to /Users/nate/.berkshelf/vagrant-berkshelf/shelves/berkshelf20150722-30827-8afd9x-master1/7-zip
==> master1: Vendoring apt (2.7.0) to /Users/nate/.berkshelf/vagrant-berkshelf/shelves/berkshelf20150722-30827-8afd9x-master1/apt
==> master1: Vendoring ark (0.9.0) to /Users/nate/.berkshelf/vagrant-berkshelf/shelves/berkshelf20150722-30827-8afd9x-master1/ark
==> master1: Vendoring build-essential (2.2.3) to /Users/nate/.berkshelf/vagrant-berkshelf/shelves/berkshelf20150722-30827-8afd9x-master1/build-essential
==> master1: Vendoring chef_handler (1.2.0) to /Users/nate/.berkshelf/vagrant-berkshelf/shelves/berkshelf20150722-30827-8afd9x-master1/chef_handler
==> master1: Vendoring docker (0.40.3) to /Users/nate/.berkshelf/vagrant-berkshelf/shelves/berkshelf20150722-30827-8afd9x-master1/docker
==> master1: Vendoring java (1.31.0) to /Users/nate/.berkshelf/vagrant-berkshelf/shelves/berkshelf20150722-30827-8afd9x-master1/java
==> master1: Vendoring maven (1.3.0) to /Users/nate/.berkshelf/vagrant-berkshelf/shelves/berkshelf20150722-30827-8afd9x-master1/maven
==> master1: Vendoring mesos (0.2.2) to /Users/nate/.berkshelf/vagrant-berkshelf/shelves/berkshelf20150722-30827-8afd9x-master1/mesos
==> master1: Vendoring python (1.4.6) to /Users/nate/.berkshelf/vagrant-berkshelf/shelves/berkshelf20150722-30827-8afd9x-master1/python
==> master1: Vendoring ulimit (0.3.3) to /Users/nate/.berkshelf/vagrant-berkshelf/shelves/berkshelf20150722-30827-8afd9x-master1/ulimit
==> master1: Vendoring windows (1.37.0) to /Users/nate/.berkshelf/vagrant-berkshelf/shelves/berkshelf20150722-30827-8afd9x-master1/windows
==> master1: Vendoring yum (3.6.3) to /Users/nate/.berkshelf/vagrant-berkshelf/shelves/berkshelf20150722-30827-8afd9x-master1/yum
==> master1: Vendoring yum-epel (0.6.2) to /Users/nate/.berkshelf/vagrant-berkshelf/shelves/berkshelf20150722-30827-8afd9x-master1/yum-epel
==> master1: Warning! The AWS provider doesn't support any of the Vagrant
==> master1: high-level network configurations (config.vm.network). They
==> master1: will be silently ignored.
==> master1: Warning! You're launching this instance into a VPC without an
==> master1: elastic IP. Please verify you're properly connected to a VPN so
==> master1: you can access this machine, otherwise Vagrant will not be able
==> master1: to SSH into it.
==> master1: Launching an instance with the following settings...
==> master1: -- Type: m1.small
==> master1: -- AMI: ami-51bb4d3a
==> master1: -- Region: us-east-1
==> master1: -- Keypair: AWS-KEY
==> master1: -- Subnet ID: subnet-sanitized
==> master1: -- Private IP: 10.99.19.11
==> master1: -- Security Groups: ["sg-sanitized"]
==> master1: -- Block Device Mapping: []
==> master1: -- Terminate On Shutdown: false
==> master1: -- Monitoring: false
==> master1: -- EBS optimized: false
==> master1: -- Assigning a public IP address in a VPC: false
==> master1: Warning! Vagrant might not be able to SSH into the instance.
==> master1: Please check your security groups settings.
There was an error talking to AWS. The error message is shown
below:

InUse => Address 10.99.19.11 is in use.