Think about the following situation. You need to modify the address of your internal DNS server and therefore you need to change /etc/resolv.conf on all your Linux boxes. It might be that this change will not be recognized by every service running on your Linux box. Oracle for instance is a good example where you have to restart your database after such change because Oracle loads the DNS information once the database is started. So Oracle would querry your old DNS server IP unless you restart the database.
There are several ways to find out which process requests your old DNS server. Here I will explain how to utilize auditd on Red Hat derivatives to find out short living DNS requests via UDP. Continue reading
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:
Currently Satellite in version 6.1.7 does not provide an UEFI capable PXE / DHCP Server. There is a workaround in place but unfortunately after each update to the next Satellite version all these settings will be overridden. The workaround is described in this Red Hat KCS article.
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).
This feature is really nice because there was often some discussion with customers regarding the former Two-way-trust (which was actually no real two-way-trust!!!). Here you can read more about new features in IPA in latest RHEL 7.2.
A lot of colleagues are blogging about RHEL at http://rhelblog.redhat.com/. Take your time to read some interesting posts.
Unfortunately Puppet is not able to handle the installation of Yum package groups like “Base” or “compat-libraries” and so forth. This is due to the fact that Puppet is currently not able to verify if all packages in a package group are installed after a Puppet run. Continue reading
Today Red Hat shipped Satellite 6.1.7. The corresponding RHSA for Satellite is RHSA-2016:0174, for Satellite Tools it is RHBA-2016:0173.
Happy upgrading 🙂
This is something I will test out during the next days. Read this Red Hat article to know how to realize this scenario.