Description of problem: Cannot start lab controller processes in devel env because message_bus tried to load default conf file Version-Release number of selected component (if applicable): 0.9 How reproducible: All the time Steps to Reproduce: 1.cd Labcontroller/procy/src 2. PYTHONPATH=:.:./../Common python bkr/labcontroller/watchdog.py --foreground --config=../labcontroller.conf 3. Actual results: packages is being added to sys.path __import__('pkg_resources').declare_namespace(__name__) Traceback (most recent call last): File "bkr/labcontroller/watchdog.py", line 20, in <module> from bkr.labcontroller.message_bus import LabBeakerBus File "/home/rmancy/dev/beaker/LabController/proxy/src/bkr/labcontroller/message_bus.py", line 22, in <module> conf = get_conf() File "/home/rmancy/dev/beaker/LabController/proxy/src/bkr/labcontroller/config.py", line 22, in get_conf load_conf() File "/home/rmancy/dev/beaker/LabController/proxy/src/bkr/labcontroller/config.py", line 16, in load_conf _conf.load_from_file(conf_file) File "/usr/lib/python2.6/site-packages/kobo/conf.py", line 117, in load_from_file fo = open(file_name, "r") IOError: [Errno 2] No such file or directory: '/etc/beaker/labcontroller.conf' Expected results: watchdog should run Additional info:
Bulk reassignment of issues as Bill has moved to another team.
It would be good to fix this. We need to make sure we don't read any config at global scope (message_bus.py is doing that, which is why it breaks).
The bkr.labcontroller.message_bus module still exists, and still has this problem, but it's not used anywhere... is there any reason we should keep it?