Add Puppet Labs Repo to Satellite/Spacewalk

I specifically did this on my Spacewalk system (not Satellite) but I assume the procedure is the same.

NOTE: If someone feels this is not a valid approach to this, please let me know and I will update the approach or take it down.

- You do NOT need to do this part -
I downloaded and installed the Puppet RPM to gather info regarding their public repo

sudo rpm -ivh http://yum-enterprise.puppetlabs.com/el/6/extras/x86_64/puppetlabs-enterprise-release-extras-6-2.noarch.rpm

- You do NOT need to do this part -

I only imported that RPM to get the following info (/etc/yum.repos.d/puppetlabs.repo)

[puppetlabs-products]

name=Puppet Labs Products El 6 - $basearch
baseurl=http://yum.puppetlabs.com/el/6/products/$basearch
gpgkey=file:///etc/pki/rpm-gpg/RPM-GPG-KEY-puppetlabs
enabled=1
gpgcheck=1

I also used the name of the repo they have chosen.

Then login to your Spacewalk admin portal, click on

Channels | Manage Software Channels | Manage Repositories

Add the URL and Label (I labeled mine Puppet Labs Products EL 6 - I don't have RHEL 5)

Then, we need to add a channel (using data from above)

Click on Manage Software Channels and create new channel (upper right hand side)

Channel Name: Puppet Labs Products EL 6

Channel Label: puppetlabs-products

Parent Channel: CentOS 6

Arch: x86_64

Channel Summay: Puppet Labs Products EL 6

GPG key URL: http://pool.sks-keyservers.net:11371/pks/lookup?op=get&search=0x1054B7A24BD6EC30

GPG key ID: 4BD6EC30

GPG key Fingerprint: 47B3 20EB 4C7C 375A A9DA E1A0 1054 B7A2 4BD6 EC30

Then, create a repo
Click Channels | Manage Software Channels | Manage Repositories
click create new repository
Repository Label: puppetlabs-products
Repository URL: http://yum.puppetlabs.com/el/6/products/x86_64

Now - last step - associate the Repo with a Channel
Click on Manage Software Channels and select the Puppet Labs Channel under RHEL/CENTOS 6.
Once there, click on Repositories and finally click Update Repositories
Click Sync and Sync Now

- This is a hack/work-around that is quicker

Once those steps have been complete, you then run

spacewalk-repo-sync --type=yum --url='http://yum.puppetlabs.com/el/6/products/x86_64' --channel='puppetlabs-products'

Your Puppet Labs Channel will now appear under CentOS 6 (or whatever base you selected) and have 0 packages until the spacewalk-repo-sync completes.

I believe I need to do the same for the "deps" Puppet Labs repo as well. (This is my first day working with Puppet).

Resources:

http://puppetlabs.com/misc/download-options

http://docs.puppetlabs.com/guides/puppetlabs_package_repositories.html

if your clients do not have external HTTP access, you will need to pull down the signing key or sign them yourself.

Download the key and save it in
satserver:/var/www/html/pub/PUPPETLABS-CERT
http://pool.sks-keyservers.net:11371/pks/lookup?op=get&search=0x1054B7A24BD6EC30

GPG key URL: http://satserver.corp.company.com/pub/PUPPETLABS-CERT
GPG key ID: 4BD6EC30

GPG key Fingerprint: 47B3 20EB 4C7C 375A A9DA E1A0 1054 B7A2 4BD6 EC30

I think.. that should work?

RHN Satellite Server (spacewalk) repomd.xml not found

"repomd.xml not found" If you add a channel, or if your RHN cache gets corrupted, and one of your guests complains that it cannot find repomd.xml for jb-ews-2-x86_64-server-5-rpm (for example) - you need to rebuild your repodata cache. Normally this is an automated job - which is exemplified by the fact that you have obviously built out your entire Satellite environment and never had to do any of the steps you are about to do. So - some prep work: Open 3 terminals to your Satellite Server and run: # Term 1 cd /var/cache/rhn watch "ls -l | wc -l" # Term 2 pwd cd /var/log/rhn tail -f rhn_taskomatic_daemon.log # Term 3 satellite-sync --channel=jb-ews-2-x86_64-server-5-rpm Once the satellite-sync has completed, you >should< see the count increment by one. If you are unlucky (like me) you will not. You then need to login to the Satellite WebUI as the satellite admin user. Click on the Admin tab (at the top) Task Schedules (on the left) fin

Install RHEL 7 on old HP DL380 g5

Someone at work had been running RHEL on an HP DL380 G5 and blew it up. After several attempts at doing an installation that made me conclude the hardware was actually bad... I kept digging for the answer. Attempt install and Anaconda could not find any disks - try a Drivers Disk (dd.img) both cciss and hpsa. -- once we did that, when the system would reboot it would say it could not find a disk. hmmm. Boot from your installation media and interrupt the startup at grub. Add hpsa.hpsa_allow_any=1 hpsa.hpsa_simple_mode=1 to the line starting with linuxefi press CTRL-X to boot. Once the system restarts after the install, you need to once again interrupt the startup and add the line from above. After the system starts, edit /etc/default/grub and add those 2 parameters to the end of the line starting with GRUB_CMDLINE_LINUX (which likely has quiet at the end of the line currently). then run # cp /boot/grub2/grub.cfg /boot/grub2/grub.cfg.orig # grub2-mkconfig -o /boot/grub2

MOTD with colors! (also applies to shell profiles)

I'm not sure why I had never looked into this before, but this evening I became obsessed with discovering how to present different colored text in the /etc/motd. A person had suggested creating a shell script (rather than using special editing modes in vi, or something) and I agree that is the simplest way of getting this accomplished quickly. This most noteworthy portion of this script is the following: RESET="\033[0m" that puts the users shell back to the original color. I typically like a green text on black background. Also - a great reference for the different colors and font-type (underscore, etc...) https://wiki.archlinux.org/index.php/Color_Bash_Prompt I found this example on the web and I wish I could recall where so that I could provide credit to that person. #!/bin/bash #define the filename to use as output motd="/etc/motd" # Collect useful information about your system # $USER is automatically defined HOSTNAME=`uname -n` KERNEL=`un

Unix Revolution

Search This Blog