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?

P2V using dd for KVM-QEMU guest

Preface: I have certainly not exhaustively tested this process. I had a specific need and found a specific solution that worked. Situation: I was issued a shiny new laptop running Red Hat Enterprise Linux 7 (with Corp VPN, certs, Authentication configuration, etc...) The image was great, but I needed more flexibility on my bare metal. So, my goal was to P2V the corporate image so I could just run it as a VM. * Remove corporate drive and install new SSD * install corp drive in external USB-3 case * Install RHEL 7 on new SSD * dd old drive to a disk-image file in a temp location which will be an image which is the same size as your actual drive (unless you have enough space in your destination to contain a temp and converted image) * convert the raw disk-image to a qcow file while pushing it to the final location - this step should reduce the disk size - however, I believe it will only reduce/collapse zero-byte blocks (not just free space - i.e. if you de...

Extending SNMP to run arbitrary shell script

Why are we here... This is not likely something I would have pursued under normal circumstances. I happen to be working for a customer/client who is not afforded a lot of flexibility to accomplish their goals. In this case, the rigor is justified. They have to sometimes be fairly creative with how they solve problems. In this case they would like to utilize an existing snmp implementation to execute a command (or shell script) on a remote system. They came to me with the idea of using Net-SNMP extend. https://access.redhat.com/documentation/en-US/Red_Hat_Enterprise_Linux/6/html/Deployment_Guide/sect-System_Monitoring_Tools-Net-SNMP-Extending.html NOTE: This is NOT a good implementation strategy in the "real world" it will simply allow you to test the functionality. There are a TON of security implications which would need to be taken in to consideration. Implementation Steps: [root@rh7tst01 ~]# yum -y install net-snmp net-snmp-utils ...

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...

Unix Revolution

Search This Blog