-
Notifications
You must be signed in to change notification settings - Fork 37
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Puppet Master could not be reached. #31
Comments
I am also having this issue, have you found solution for this? |
Hello, |
Thanks for your update, I have raised it as an issue here also, hopefully I will get some response. I was hoping to use puppet enterprise which I'm not sure is possible with sandbox, need to do further investigation but this will work for now, thanks. |
Don't know if it is still needed but anyway.. |
Right! The problem here is that the firewall is on by default, and the puppet enterprise installer is not managing it. No manual changes should be necessary, but for sure this one bit me too. On CentOS 7, the workaround to disable the firewall is:
Then, as noted you can |
Dear Adrien,
Thanks for developing Oscar for us, I really would like to use it to experiment a bit. But, when I try to install it and run "vagrant up", whatever I try, I keep getting this message:
!! ERROR: Puppet Master at 'puppet:8140' could not be reached.
Aborting installation as directed by answer file. Set
'q_fail_on_unsuccessful_master_lookup' to 'n' if installation
should continue despite communication failures.
I also tried to change the roles.yaml file to add the master to the (first and only) agent, but also that one failed.
Thanks in advance,
Filip Moons
The text was updated successfully, but these errors were encountered: