Hi All,

I have a Vagrantfile (lets call this Vagrantfile_1.0), where in I am using 
"private_network" with a static IP. I use this box usually to create new 
boxes with certain packages installed for different use cases. For 
installing packages, I usually run "puppet apply" manually inside the box, 
and then use "vagrant package" command for packaging.

So now, I have a Puppet module for mysql. I ran puppet apply with a 
manifest that uses the mysql module and configures the box to run mysql. 
After this, I packaged the box to create a separate box file so that I can 
distribute it. Remember that I used "private_network" with static IP 
address.

Then I create a new Vagrantfile (lets call this Vagrantfile_2 for avoiding 
confusion), this time with "private_network" and DHCP settings and uses the 
box generated in the above process. "vagrant up" provisioned the box but is 
unable to SSH in. Then I tried running the VM manually using VirtualBox, 
logged in and saw that the VM is still using the old static IP address that 
I used to package this box.

After this, I went to the old box, edited the old Vagrantfile to start 
using DHCP (lets call this edited Vagrantfile as Vagrantfile_1.1), ran 
mysql manifest again, packaged it. Then used this box with the 
Vagrantfile_2, and the VM still uses the static IP address.

I am not really sure if I am doing something wrong, or if this is a bug in 
Vagrant. Would appreciate some help on this. Here are the Vagrantfiles:
- Vagrantfile_1.0 - 
https://www.dropbox.com/s/rhan6ciu1ci75ch/Vagrantfile_1.0?dl=0
- Vagrantfile_1.1 - 
https://www.dropbox.com/s/s4ff52v3op27gth/Vagrantfile_1.1?dl=0
- Vagrantfile_2 - 
https://www.dropbox.com/s/7opfjzve5gw3n1w/Vagrantfile_2?dl=0

Thanks,
Vaidik

-- 
You received this message because you are subscribed to the Google Groups 
"Vagrant" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to [email protected].
For more options, visit https://groups.google.com/d/optout.

Reply via email to