Description of problem: The hwcert realtime test fails with a python traceback: TypeError: cannot concatenate 'str' and 'NoneType' objects Version-Release number of selected component (if applicable): redhat-certification-2.3-20160223.el7.noarch redhat-certification-hardware-1.7.1-20160210.el7.noarch How reproducible: realiably on at least one test system Steps to Reproduce: 1. run the hwcert realtime test 2. check logs or debug output 3. Actual results: crash with traceback: File "/usr/lib/python2.7/site-packages/rhcert/client/harness.py", line 573, in _doRun returnValue = self.runTest(logDirectory, testDocument, runDocument, outputFilePath) File "/usr/lib/python2.7/site-packages/rhcert/client/harness.py", line 1001, in runTest rv = test.run() File "/usr/lib/python2.7/site-packages/rhcert/suites/hwcert/tests/realtime/realtime.py", line 101, in run from rteval import RTEVAL_VERSION File "/usr/lib/python2.7/site-packages/rteval/__init__.py", line 37, in <module> from modules.loads import LoadModules File "/usr/lib/python2.7/site-packages/rteval/modules/__init__.py", line 26, in <module> from rteval.rtevalConfig import rtevalCfgSection File "/usr/lib/python2.7/site-packages/rteval/rtevalConfig.py", line 82, in <module> 'srcdir' : default_config_search(['loadsource']), File "/usr/lib/python2.7/site-packages/rteval/rtevalConfig.py", line 41, in default_config_search (os.getenv('SUDO_USER') or os.getenv('USER'))), '.rteval'), TypeError: cannot concatenate 'str' and 'NoneType' objects Expected results: test runs to completion and succeeds Additional info:
Created attachment 1146993 [details] patch to handle sparse environment in hwcert test suite
Note, the above patch will go into rteval-2.8
Added to rteval build 2.8
Created attachment 1202917 [details] local function to return string value when determining user name
The above patch adds the local function get_user_name() which handles empty environment variables SUDO_USER and USER. This patch modifies the original patch and will be available in the next build of rteval (2.12).
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://rhn.redhat.com/errata/RHBA-2016-2244.html
*** Bug 1418811 has been marked as a duplicate of this bug. ***