Welcome

Hi guys,

welcome to my personal blog. Here you can find some information about my person and my work. Currently I`m employed as an Infrastructure Architect at Kühne + Nagel in Hamburg.

Here you will find a lot of technical stuff on my blog. Please notice that any information and documentation you can find here are my personal view. Nothing is related to my current employer. If you use any of the things I`m posting here is on your own risk.

RHEL 7 supports online disk resize with active partition tables on disk

One of the interesting features in RHEL 7 is the fact that it supports online disk re-sizing even if there is an active partitioning table on the disk. This feature is interesting in case you want to re-size your virtual disk. You can do this online for example in VMWare. If you have a LVM partition on the disk you want to resize then you need to perform the steps described in this article from Red Hat.

In order to resize online a partition which is in use please observe the following steps:

Continue reading “RHEL 7 supports online disk resize with active partition tables on disk”

Satellite 6 => OS release version not attached to a copied Activation Key correctly

Currently there seems to be a bug in Satellite 6 (6.1.6). I`ve created an Activation Key and attached a “Release Version” on the Details tab to the Activation Key. I also configured all other needed things like product content, subscriptions and so on.

If I now copy this Activation Key the Release Version seems to be present at the copied Activation Key. But when I try to install a new client with the copied Activation Key which for example has 7.2 as a release version then the client does not configure the release version via subscription-manager correctly during provisioning. This leads to the problem that the client is not able to access the correct RHEL Yum repositories on Satellite.

If I open the copied Activation Key again, delete the release version and attach the release version again, then the client can successfully access all needed Yum repositories with this specific release version during provisioning.

I filled an appropriate BZ entry (BZ 1311846).