Red Hat Bugzilla – Bug 969962
When the hostname and resolv.conf on the machine change, rhts-sync-set -s DONE in rhts-test-runner.sh blocks indefinitely
Last modified: 2018-02-05 19:41:31 EST
Description of problem:
I have multihost tests that test DNS servers. Part of that test is to setup new DNS server, have forwarders point to the original nameserver from resolve.conf so that the global resolution still works, defining my own domain (example.com) and changing the hostname of the machine to be withing that example.com domain.
My tests then start to block at the point where the whole test (within a job) is run and the job should move to the next test. I've identified the
rhts-sync-set -s DONE
call in /usr/bin/rhts-test-runner.sh to be the culprit since it uses the current $HOSTNAME which it identified by running hostname command, and that value points to .example.com, and Marian says that something does not identify correctly that there is a new record in resolv.conf which would be able to resolve that hostname.
Version-Release number of selected component (if applicable):
Steps to Reproduce:
1. Have two-host job, on one machine create DNS server, have it use resolv.conf's nameserver(s) as forwarders, create two records in the DNS server, point both hosts to that DNS server (edit resolv.conf), change hostnames on that server.
2. Have additional two test after this one in the job.
The job will never move from the first additional test to the second one. Running ps on that machine will show
rhts-sync-set -s DONE
stuck and blocking.
It should work.
This is mostly about rhts-test-env which I'm not sure belongs to the product Beaker, component test harness. Please realign if there's better place for this bugzilla.
Please consider patches
--- /usr/bin/rhts-environment.sh.orig 2013-04-05 02:55:07.000000000 -0400
+++ /usr/bin/rhts-environment.sh 2013-05-30 13:22:20.481051448 -0400
@@ -30,6 +30,13 @@
+if [ -f /etc/original-hostname ]; then
+ export ORIGINAL_HOSTNAME=$( cat /etc/original-hostname )
+ export ORIGINAL_HOSTNAME=$HOSTNAME
+ echo $ORIGINAL_HOSTNAME > /etc/original-hostname
if [ -z "$ARCH" ]; then
--- /usr/bin/rhts-sync-set.orig 2013-04-05 02:55:07.000000000 -0400
+++ /usr/bin/rhts-sync-set 2013-05-30 13:24:16.242686978 -0400
@@ -80,7 +80,9 @@
recipesetid = os.environ['RECIPESETID']
if ('TESTORDER' in os.environ.keys()):
testorder = os.environ['TESTORDER']
- if ('HOSTNAME' in os.environ.keys()):
+ if ('ORIGINAL_HOSTNAME' in os.environ.keys()):
+ hostname = os.environ['ORIGINAL_HOSTNAME']
+ elif ('HOSTNAME' in os.environ.keys()):
hostname = os.environ['HOSTNAME']
args = sys.argv[1:]
which "fixates" the original HOSTNAME in the ORIGINAL_HOSTNAME variable and uses that variable as the default hostname in rhts-sync-set.
Note that this also makes it much easier to check if the machine is part of some role (SERVERS, CLIENTS, whatever you put to the role attribute) by using $ORIGINAL_HOSTNAME while using $HOSTNAME or $(hostname) no longer works.
I might have needed the patch
--- /usr/lib/python2.6/site-packages/beah/tasks/rhts_xmlrpc.py.orig 2013-04-05 02:43:26.000000000 -0400
+++ /usr/lib/python2.6/site-packages/beah/tasks/rhts_xmlrpc.py 2013-05-31 05:28:09.676218239 -0400
@@ -288,7 +288,7 @@
def __init__(self, main):
self.main = main
- self.localhosts = (main.env.get('HOSTNAME', ''), os.environ.get('HOSTNAME', ''))
+ self.localhosts = (main.env.get('HOSTNAME', ''), os.environ.get('HOSTNAME', ''), os.environ.get('ORIGINAL_HOSTNAME', ''))
def trhostname(self, hostname):
if hostname in self.localhosts:
in the past as well but I'm not 100 % sure about that -- I assume developers fluent in the beah code should know for sure.
Thanks for the ideas/patches Jan. I think they sound good in theory.
Many tasks are using $HOSTNAME but it's problematic because (a) it's bash-specific, (b) it's set once to whatever the hostname was at the time the shell started, (c) it's *not* the fully-qualified domain name, unless the DHCP config has caused the hostname to be set to a FQDN (which is not always the case).
A better option is $(hostname -f) but as you point out in this bug, very often what the task really wants is the hostname from Beaker's point of view, not whatever glibc thinks the current DNS FQDN is.
I wonder if $BEAKER_HOSTNAME might be a better name than $ORIGINAL_HOSTNAME. We need to consider how it fits in with the other environment variables defined by Beaker.
(In reply to Dan Callaghan from comment #4)
> I wonder if $BEAKER_HOSTNAME might be a better name than $ORIGINAL_HOSTNAME.
> We need to consider how it fits in with the other environment variables
> defined by Beaker.
Sure, BEAKER_HOSTNAME will do just as well.
*** Bug 1045010 has been marked as a duplicate of this bug. ***