Differences

This shows you the differences between two versions of the page.

--- pub:ubuntu_14.04_campus_build [2015/04/06 20:37]
rlhaffer
+++ pub:ubuntu_14.04_campus_build [2022/05/06 20:15] (current)
@@ Line 1: / Line 1: @@
-====== Campus Ubuntu 14.04 Foreman/Puppet Installation ======
+====== Campus Ubuntu 14.04 Foreman & Puppet Installation ======
 The current 14.04 build has been tested on:
@@ Line 57: / Line 57: @@
 {{:pub:foreman-1.png?900|}}
-As the image boots, when it gets to the point where you see what is in the **<fc #ffff00>yellow box</fc>**, the system has sent the requests back to the Foreman server.  This may take a minute or so.
+As the image boots, when it gets to the point where you see what is in the <html><span style="color: #ffd500; background-color: #001111; padding: 0px 3px"><strong>yellow box</strong></span></html>, the system has sent the requests back to the Foreman server.  This may take a minute or so.
 {{:pub:foreman-2-edit.png?900|}}
+We have hostname based provisioning configured, however if you are using a custom host name you may be required to use the steps below regarding discovered hosts. You will know this to be the case if the host doesn't automatically reboot after a few seconds of displaying the portion in the yellow box.\\
 Back on the Foreman website, click on the **Hosts > Discovered Hosts** menu.
@@ Line 134: / Line 136: @@
 {{:pub:duringinstallation.png?700|}}
-This screen is somewhat deceiving.  The build is still going and will probably run for about an hour, depending on your connection speed.  One real hardware, you will see the hard drive activity light constantly flashing during the build.  When it is complete, the activity will slow down, you will see a login screen, and you can check the All Hosts page in Foreman and if it has an **O** (for online) the system is built.\\
+This screen is somewhat deceiving.  The build is still going and will probably run for about an hour, depending on your connection speed.  On real hardware, you will see the hard drive activity light constantly flashing during the build.  When it is complete, the activity will slow down, you will see a login screen, and you can check the **All Hosts** page in Foreman and if it has a <fc #00ff00>green **O** (for online)</fc> the system is built.\\
 {{:pub:foremanonline.png|}}
@@ Line 141: / Line 143: @@
 {{:pub:loginscreen.png?900|}}
+At this point, the system is ready to be logged into.\\
+There are more finer points to the build, like the S drive, printers and adding other software from the Ubuntu repos or elsewhere.\\
+Those tutorials are in process.\\
+=====Adding Software=====
+Adding supported software titles to an existing installation is as easy as editing the host in foreman, visit [[https://rssinst.srv.mst.edu]], sign in, and go to the hosts tab and search for the host you would like to change.\\
+{{:pub:screenshot_from_2015-06-04_16_48_45.png?900|}}
+Then click the Puppet Classes tab and wk_pkgs, the plus button adds the package to the machine and it should begin installing inside 30 minutes of being added to the system.\\
+{{:pub:screenshot_from_2015-06-04_16_49_30.png?900|}}
+=====Troubleshooting=====
+====DNS conflict errors====
+Sometimes Foreman will not flush it's dns entries of systems that have long since changed IP addresses and the system you are trying to build will grab an IP that the Foreman server thinks is someone else. This causes a dns reverse lookup error to occur, to resolve the conflict we have to remove the offending IP from the reverse lookup table and restart the dns service on rssinst. Here's how you do that:
+<code>
+ssh rssinst.srv.mst.edu
+sudo -i
+cd /var/cache/bind/zones
+vi db.151.131.in-addr.arpa
+</code>
+In this file IP addresses are broken down by octet in reverse order, see picture:
+{{:pub:foreman-screenshot.png?600|}}
+For example, if you're looking for IP 131.151.53.112, you'll search for the header 53.151.131.in-addr.arpa and under that will be an entry for 112 and a hostname Foreman thinks is associated with that IP. Just delete that line. Please note (I don't really think you're going to do this, but CYA and all that) don't actually delete 53.112 unless that's actually the machine you're having issues with, please search for the proper 3rd and 4th octets and delete the line that is the IP of the machine actually giving you issues.
+Now save the file and go out to the system and restart the bind service.
+<code>
+service bind9 restart
+</code>
+Then retry your build attempt.

IT Research Support Solutions Wiki

User Tools

Site Tools

Differences

Page Tools