RHN Satellite Foo : removing a kickstart profile

In our environment (which I have inherited) there were 2 profiles which would be displayed as a kickstart profile, but the had a red stop sign with an X in the column that said if it was RHN Satellite Managed?

[root@prhnsat01 profiles.d]# cobbler list
distros:
ks-rhel-i386-client-5
ks-rhel-i386-client-5-u1
ks-rhel-i386-client-5-u1xen
ks-rhel-i386-client-5-u2
ks-rhel-i386-client-5-u2xen
ks-rhel-i386-client-5-u3
ks-rhel-i386-client-5-u3xen
ks-rhel-i386-client-5-u4
ks-rhel-i386-client-5-u4xen
ks-rhel-i386-client-5-u5
ks-rhel-i386-client-5-u5xen
ks-rhel-i386-client-5-u6
ks-rhel-i386-client-5-u6xen
ks-rhel-i386-client-5xen
ks-rhel-i386-server-5
ks-rhel-i386-server-5-57
ks-rhel-i386-server-5-57xen
ks-rhel-i386-server-5-58
ks-rhel-i386-server-5-58xen
ks-rhel-i386-server-5-59
ks-rhel-i386-server-5-59-rc-30
ks-rhel-i386-server-5-59-rc-30xen
ks-rhel-i386-server-5-59xen
ks-rhel-i386-server-5-u1
ks-rhel-i386-server-5-u1xen
ks-rhel-i386-server-5-u2
ks-rhel-i386-server-5-u2xen
ks-rhel-i386-server-5-u3
ks-rhel-i386-server-5-u3xen
ks-rhel-i386-server-5-u4
ks-rhel-i386-server-5-u4xen
ks-rhel-i386-server-5-u5
ks-rhel-i386-server-5-u5xen
ks-rhel-i386-server-5-u6
ks-rhel-i386-server-5-u6xen
ks-rhel-i386-server-5xen
ks-rhel-i386-server-6-60
ks-rhel-i386-server-6-61
ks-rhel-i386-server-6-62
ks-rhel-i386-server-6-63
ks-rhel-x86_64-client-5
ks-rhel-x86_64-client-5-u1
ks-rhel-x86_64-client-5-u1xen
ks-rhel-x86_64-client-5-u2
ks-rhel-x86_64-client-5-u2xen
ks-rhel-x86_64-client-5-u3
ks-rhel-x86_64-client-5-u3xen
ks-rhel-x86_64-client-5-u4
ks-rhel-x86_64-client-5-u4xen
ks-rhel-x86_64-client-5-u5
ks-rhel-x86_64-client-5-u5xen
ks-rhel-x86_64-client-5-u6
ks-rhel-x86_64-client-5-u6xen
ks-rhel-x86_64-client-5xen
ks-rhel-x86_64-server-5
ks-rhel-x86_64-server-5-57
ks-rhel-x86_64-server-5-57xen
ks-rhel-x86_64-server-5-58
ks-rhel-x86_64-server-5-58xen
ks-rhel-x86_64-server-5-59
ks-rhel-x86_64-server-5-59-rc-30
ks-rhel-x86_64-server-5-59-rc-30xen
ks-rhel-x86_64-server-5-59xen
ks-rhel-x86_64-server-5-u1
ks-rhel-x86_64-server-5-u1:xen
ks-rhel-x86_64-server-5-u2
ks-rhel-x86_64-server-5-u2:xen
ks-rhel-x86_64-server-5-u3
ks-rhel-x86_64-server-5-u3:xen
ks-rhel-x86_64-server-5-u4
ks-rhel-x86_64-server-5-u4:xen
ks-rhel-x86_64-server-5-u5
ks-rhel-x86_64-server-5-u5:xen
ks-rhel-x86_64-server-5-u6
ks-rhel-x86_64-server-5-u6xen
ks-rhel-x86_64-server-5:xen
ks-rhel-x86_64-server-6-60
ks-rhel-x86_64-server-6-61
ks-rhel-x86_64-server-6-61-beta
ks-rhel-x86_64-server-6-62
ks-rhel-x86_64-server-6-63
ks-rhel-x86_64-server-6-64
ks-rhel-x86_64-server-6-beta-61-beta

profiles:
Desktop:1:XYZCo
VLAN144:1:XYZCo
VLAN184:1:XYZCo
VLAN192:1:XYZCo
VLAN192v:1:XYZCo
VLAN196:1:XYZCo
VLAN198:1:XYZCo
VLAN20:1:XYZCo
VLAN40:1:XYZCo
VLAN80:1:XYZCo
kickstart5:1:XYZCo
kickstart5kvm:1:XYZCo
kickstart5nj:1:XYZCo
kickstart5vmware:1:XYZCo
kickstart6-620nj:1:XYZCo
kickstart6:1:XYZCo
kickstart6kvm:1:XYZCo
kickstart6nj:1:XYZCo
kickstart6vmware:1:XYZCo
kickstart:1:XYZCo

systems:
pwebdba01.corp.xyxco.com:1

repos:

images:
[root@prhnsat01 profiles.d]# cobbler profile remove --name Desktop:1:XYZCo
[root@prhnsat01 profiles.d]# cobbler profile remove --name kickstart6-620nj:1:XYZCo

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

Unix Revolution

Search This Blog