Skip to main content

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 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?
Labels:

Comments

Post a Comment

Popular posts from this blog

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...
1 comment
Read more

Sun USS 7100 foo

TIP: put ALL of your LUNs into a designated TARGET and INITIATOR group when you create them.  If you leave them in the "default" group, then everything that does an discovery against the array will find them :-( I'm struggling to recognize a reason that a default should even be present on the array. Also - who, exactly, is Sun trying to kid.  The USS is simply a box.. running Solaris .. with IPMP and ZFS.  Great.  If you have ever attempted to "break-in" or "p0wn" your IBM HMC, you know that there are people out there that can harden a box - then.. there's Sun.  After a recent meltdown at the office I had to get quite intimate with my USS 7110 and learned quite a bit.  Namely: there's a shell ;-) My current irritation is how they attempt to "warn you" away from using the shell (my coverage expired a long time ago to worry about that) and then how they try to hide things, poorly. I was curious as to what version of SunOS it ...
1 comment
Read more

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)"

"Error getting authority: Error initializing authority: Could not connect: No such file or directory (g-io-error-quark, 1)" One issue that may cause this to arise is if you managed to break your /etc/fstab We had an engineer add a line with the intended options of "nfsvers=3" but instead added "-onfsvers=3" and it broke the system fairly catastrophically.
Post a Comment
Read more