Hide Forgot
From the console log, it seems the error is: + /usr/bin/rhts-test-runner.sh HOSTNAME is not defined + rc=1
... which makes it a dupe of bug 1072260 (which was CLOSED WORKSFORME because we couldn't figure out how to reproduce it).
Marian, just wondering if this means there really was a bug in some RHEL component causing HOSTNAME not to be set? Or just the problem is non reproducible? I think we could work around it in the rhts scripts, if necessary -- I was just trying to understand exactly how it can happen.
(In reply to Dan Callaghan from comment #5) > Marian, just wondering if this means there really was a bug in some RHEL > component causing HOSTNAME not to be set? Or just the problem is non > reproducible? > > I think we could work around it in the rhts scripts, if necessary -- I was > just trying to understand exactly how it can happen. Sorry for so "brief" closing comment, it wasn't intentional (just quick fingers and couple of tasks made in parallel). So far we reported another Bug 1388037 against RHEL-6.9, that one could be cause also of issue described here (later we noticed also missing login prompt in console.log, that was clue). While having harness resistent to possible issues would be clear advantage (easier debugging, more tests executed, ...), according to description from that another bug I expect this specific issue can't be perfectly avoided unfortunately (despite to success of restraint). Last but not least, curiously the example with restraint provided by Bill revealed that a 'more robust' harness could lead to false negative (missed issue). If you look into console.log of Bill's job, you won't find login: prompt either (== likely affected by same issue)
I think having an actual test case for this situation is better than relying on the test infrastructure to happen to show it.
Okay, so to sum up... the fact that beah relies on HOSTNAME being set is fine, because bash promises that, so it's a bug (somewhere) in the distro if HOSTNAME is not set. The fact that restraint doesn't rely on HOSTNAME being set is fine too, it's just an implementation choice in the harness. Therefore this is NOTABUG. Right?