There was a new submodule added to resultsdb since the last release but the setup.py was not updated to account for this. Now, running the resultsdb cli with the most recent release causes tracebacks:
setup.py
# RESULTSDB_CONFIG=/etc/resultsdb/settings.py resultsdb upgrade_db doing stream logging /usr/lib/python2.7/site-packages/flask_sqlalchemy/__init__.py:800: UserWarning: SQLALCHEMY_TRACK_MODIFICATIONS adds significant overhead and will be disabled by default in the future. Set it to True to suppress this warning. warnings.warn('SQLALCHEMY_TRACK_MODIFICATIONS adds significant overhead and will be disabled by default in the future. Set it to True to suppress this warning.') Traceback (most recent call last): File "/usr/bin/resultsdb", line 9, in <module> load_entry_point('resultsdb==2.0.3', 'console_scripts', 'resultsdb')() File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 547, in load_entry_point return get_distribution(dist).load_entry_point(group, name) File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2720, in load_entry_point return ep.load() File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2380, in load return self.resolve() File "/usr/lib/python2.7/site-packages/pkg_resources/__init__.py", line 2386, in resolve module = __import__(self.module_name, fromlist=['__name__'], level=0) File "/usr/lib/python2.7/site-packages/resultsdb/__init__.py", line 141, in <module> from resultsdb.controllers.api_v2 import api as api_v2 File "/usr/lib/python2.7/site-packages/resultsdb/controllers/api_v2.py", line 39, in <module> from resultsdb.lib.helpers import non_empty, dict_or_string, list_or_none ImportError: No module named lib.helpers
Fix the setup.py file to have 'resultsdb.lib' in the list of packages, do another release and submit new builds to koji
'resultsdb.lib'
Should be fixed in d39eadc.
Login to comment on this ticket.