Closed LinguineCode closed 9 years ago
Good catch, hosts_add.pp handles this for manual steps and was missed in the bootstrap. That file should be called instead, if you want to revise your PR. Otherwise, I'll look into that shortly.
I see that manifest now. Where is the IP 10.0.0.5
coming from though?
That matches the sample DNS zone files that are included in dist/profile.
Rob Nelson rnelson0@gmail.com
On Wed, Sep 2, 2015 at 12:04 AM, Sean S. King notifications@github.com wrote:
I see that manifest now. Where is the IP 10.0.0.5 coming from though?
— Reply to this email directly or view it on GitHub https://github.com/puppetinabox/controlrepo/pull/46#issuecomment-136932563 .
If I understand correctly...the problem is my brand new VM doesn't know about that IP yet until Puppet runs the first time and sets the IP. Chicken/egg
That is correct, and it wouldn't. The file is helpful not just on the master but on other nodes until the DNS node is setup, so hosts_add.pp, hosts_remove.pp, and the zone files should have consistency. I think 'puppet apply hosts_add.pp' would suffice.
Rob Nelson rnelson0@gmail.com
On Wed, Sep 2, 2015 at 10:05 AM, Sean S. King notifications@github.com wrote:
If I understand correctly...the problem is my brand new VM doesn't know about that IP yet until Puppet runs the first time and sets the IP. Chicken/egg
— Reply to this email directly or view it on GitHub https://github.com/puppetinabox/controlrepo/pull/46#issuecomment-137092937 .
@seanscottking I also think that 127.0.1.1 is a Debian/Ubuntu thing - Red Hat doesn't add that to the localhost. Do you still think this is needed, and if so can you rework it to use hosts_add.pp
?
I'm going to close this. If you feel this is still needed, open a new PR that uses host_add.pp
please. Thanks!
After
./bootstrap.sh
,puppet agent -t
won't won't work because it can't resolve the host "puppet." This PR adds a line to /etc/hosts so we can resolve puppet => localhost