The Puppet installation process can be quite simple
— as long as everything is set up properly to begin with. However, when we go to perform what should be simple tasks, things can go wrong. In this hands-on lab, we will explore what happens when our Puppet Enterprise install doesn’t go the way we expect it to. We will also examine what steps we can take to pinpoint the problem, fix it, and then get Puppet back to an operational state.
Learning Objectives
Successfully complete this lab by achieving the following learning objectives:
- Attempt to Install Puppet Enterprise
Attempt to run the installer and access the graphical install:
cd puppet-enterprise-2018.1.7-el-7-x86_64/ sudo ./puppet-enterprise-installer- When we try to access the console, it will time out. Return to the command line and cancel the installer with (CTRL+C).
- Check the Firewall
Check the status of the firewall:
$ sudo firewall-cmd --stateSince the firewall is being enforced, we cannot access the installer. Let’s assume we will update our firewall ports via a Puppet post-install, so just stop it using the following
firewalldcommands:$ sudo systemctl stop firewalld $ sudo systemctl disable firewalld
- Check the Hosts File
Attempt to run the installer again. This time the graphical installer works, but Puppet cannot connect to
puppet.ec2.internal. We need to update the/etc/hostsfile:$ sudo vim /etc/hosts 127.0.0.1 puppet.ec2.internal localhost localhost.localdomain localhost4 localhost4.localdomain4- Return to the console and run the installer. We should see Puppet Enterprise install this time.
