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

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.

Unix Revolution

Search This Blog