Skip to main content

register your RHEL client to Red Hat (after being reg'd to a Satellite)

Solution:  remove the up2date configuration, run rhn_register, then select the certificate at /usr/share/rhn/RHNS-CA-CERT

Issue:
When I first installed RHEL on my laptop I registered it to the Satellite I have at my house, behind a firewall.  I have a problem leaving my own Satellite exposed to the Internet as if someone found it, they could poach software off the thing whenever they like.  Normally having my laptop reg'd to my own Satellite is fine as I am home quite often.  However, today I had a need to install telnet and I am at my office.  I could open the firewall back to my house from the office, but I instead decided to register my laptop back to Red Hat since I have available entitlements.

# rpm -qa | grep rhn

# rpm -e rhn-org-trusted-ssl-cert-1.0-1.noarch
# cd /etc/sysconfig/rhn; mv up2date up2date.previous
# rhn_register

Then tell the app to use the cert located at /usr/share/rhn/RHNS-CA-CERT

Comments

Popular posts from this blog

PXE boot a LiveCD image

Summary: I have wanted to build a kickstart environment which hosted a "rescue CD" or LiveCD to allow you to boot over the network after you blew your stuff up and needed to repair a few things.  Today I have worked through a method of doing so, with the help of the people who published a succinct script with the Red Hat Enterprise Virtualization Hypervisor.  (the script will be at the bottom of this post - if I have somehow not followed the GPL, please let me know and I will correct whatever is necessary) NOTE/Warning: The boot will fail due the initrd being too large (645mb).  I'm not sure how to proceed.  This procedure worked for RHEVh, because it is quite a bit smaller.  Hopefully I can report back with progress on this? :-$ Procedure: download your LiveCD image to /export/isos/RESCUE/Fedora-16-i686-Live-Desktop.iso # cd /var/tmp # vi livecd-iso-to-pxeboot (populate the file with the script shown below) # chmod 754 ./livecd-iso-to-pxeb...

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

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