Skip to main content

RHN Satellite Registration for client

You will need to first do the following:
  • Create Activation Keys
  • (https://rhnsat.host.com/rhn/activationkeys/List.do)
Then - on your RHNSAT host
[root@rhnsat ~]# rhn-bootstrap --activation-keys 1-GetYourOwnKey --gpg-key /var/www/html/pub/RHN-ORG-TRUSTED-SSL-CERT --allow-config-actions --allow-remote-commands
* bootstrap overrides (written):
'/var/www/html/pub/bootstrap/client-config-overrides.txt'

Values written:
enableProxy '0'
serverURL 'https://rhnsat.host.com/XMLRPC'
proxyPassword ''
proxyUser ''
sslCACert '/usr/share/rhn/RHN-ORG-TRUSTED-SSL-CERT'
httpProxy ''
noSSLServerURL 'http://rhnsat.host.com/XMLRPC'
enableProxyAuth '0'
useGPG 1

* bootstrap script (written):
'/var/www/html/pub/bootstrap/bootstrap.sh'

on the client
wget http://rhnsat.host.com/pub/bootstrap/bootstrap.sh
/bin/bash ./bootstrap.sh
yum list

UPDATE:
If you need to re-register your system (in my case I rebuilt my RHN Satellite system, with the same hostname, etc... because this is, in fact, my lab...)

You need to remove the SSL cert previously installed.

[root@neo ~]# rpm -qa | grep rhn
rhn-setup-gnome-1.0.0-73.el6.noarch
rhnsd-4.9.3-2.el6.x86_64
yum-rhn-plugin-0.9.1-36.el6.noarch
rhnlib-2.5.22-12.el6.noarch
rhn-org-trusted-ssl-cert-1.0-1.noarch
rhn-client-tools-1.0.0-73.el6.noarch
rhn-setup-1.0.0-73.el6.noarch
rhn-check-1.0.0-73.el6.noarch
[root@neo ~]# rpm -e rhn-org-trusted-ssl-cert-1.0-1.noarch
[root@neo ~]# wget 10.10.31.100/pub/bootstrap/bootstrap.sh
[root@neo ~]# /bin/bash ./bootstrap.sh

Comments

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

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

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