Hello,
I've observed something odd. Here it is. So Initially I used most basic
vagrantfile and created VM. This vagrant file location is /media/../test
Vagrant.configure("2") do |config|
config.vm.box = "hashicorp/precise64"
config.vm.provision :shell, path: "bootstrap.sh"
config.vm.network "forwarded_port", guest: 80, host: 3456
end
This created a VM with default hostname precise64
I then edited vagrant file and added config.vm.hostname parameter and set
the hostname to ubu-vm1. After this, I ran vagrant reload and sure enough
the hostname was changed to ubu-vm1.
But after commenting config.vm.hostname and doing "vagrant reload" it did
not change hostname back to default.
When I introduced few parameters for CPU (like no of CPU/CPU cap) all those
changes were effective upon "vagrant reload". My VM had 1 CPU and 50% cap.
Surprisingly, when I did vagrant reload after commenting these parameters
in the vagrant file, things remained same. my VM still had 1 CPU and 50%
cap.
BUG? Why is vagrant still reading values which are not present in current
file? I am running vagrant 2.0.0 on Linux Mint 18.3.
Note:- When I destroy VM vagrant destroy and then do vagrant up, then files
it only picksup whatever is defined in file.
--
Makrand
--
This mailing list is governed under the HashiCorp Community Guidelines -
https://www.hashicorp.com/community-guidelines.html. Behavior in violation of
those guidelines may result in your removal from this mailing list.
GitHub Issues: https://github.com/mitchellh/vagrant/issues
IRC: #vagrant on Freenode
---
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].
To view this discussion on the web visit
https://groups.google.com/d/msgid/vagrant-up/CABdC_7%3D9rAomcVRfgWeVUsKigmbqYHpEYUFd%2BzyTheDL7Ww5_A%40mail.gmail.com.
For more options, visit https://groups.google.com/d/optout.
