Unable to execute 'get_status' API using Armada Client #180
Description
Is this a bug report or feature request? (choose one):
This is a bug
Python Version (output of python --version):
Python 3.5.2
Development or Deployment Environment?:
Deployment Environment (CI/CD lab)
Release Tag or Master:
Master
Expected Behavior:
Armada should be able check that Tiller is up and running properly with get_status API call
What Actually Happened:
Problem seems to be related to armada config. We see the following errors in the logs of the Armada API container
*** Operational MODE: single process ***
Loading paste environment: config:/etc/armada/api-paste.ini
Traceback (most recent call last):
File "/usr/local/lib/python3.5/dist-packages/paste/deploy/loadwsgi.py", line 247, in loadapp
return loadobj(APP, uri, name=name, **kw)
File "/usr/local/lib/python3.5/dist-packages/paste/deploy/loadwsgi.py", line 271, in loadobj
global_conf=global_conf)
File "/usr/local/lib/python3.5/dist-packages/paste/deploy/loadwsgi.py", line 296, in loadcontext
global_conf=global_conf)
File "/usr/local/lib/python3.5/dist-packages/paste/deploy/loadwsgi.py", line 320, in _loadconfig
return loader.get_context(object_type, name, global_conf)
File "/usr/local/lib/python3.5/dist-packages/paste/deploy/loadwsgi.py", line 450, in get_context
global_additions=global_additions)
File "/usr/local/lib/python3.5/dist-packages/paste/deploy/loadwsgi.py", line 559, in _pipeline_app_context
APP, pipeline[-1], global_conf)
File "/usr/local/lib/python3.5/dist-packages/paste/deploy/loadwsgi.py", line 458, in get_context
section)
File "/usr/local/lib/python3.5/dist-packages/paste/deploy/loadwsgi.py", line 517, in _context_from_explicit
value = import_string(found_expr)
File "/usr/local/lib/python3.5/dist-packages/paste/deploy/loadwsgi.py", line 22, in import_string
return pkg_resources.EntryPoint.parse("x=" + s).load(False)
File "/usr/local/lib/python3.5/dist-packages/pkg_resources/init.py", line 2405, in load
return self.resolve()
File "/usr/local/lib/python3.5/dist-packages/pkg_resources/init.py", line 2411, in resolve
module = import(self.module_name, fromlist=['name'], level=0)
File "./armada/api/server.py", line 31, in
conf.set_app_default_configs()
File "./armada/conf/init.py", line 31, in set_app_default_configs
set_default_for_default_log_levels()
File "./armada/conf/init.py", line 47, in set_default_for_default_log_levels
log.register_options(CONF)
File "/usr/local/lib/python3.5/dist-packages/oslo_log/log.py", line 250, in register_options
conf.register_cli_opts(_options.common_cli_opts)
File "/usr/local/lib/python3.5/dist-packages/oslo_config/cfg.py", line 2426, in __inner
result = f(self, *args, **kwargs)
File "/usr/local/lib/python3.5/dist-packages/oslo_config/cfg.py", line 2648, in register_cli_opts
self.register_cli_opt(opt, group, clear_cache=False)
File "/usr/local/lib/python3.5/dist-packages/oslo_config/cfg.py", line 2430, in __inner
return f(self, *args, **kwargs)
File "/usr/local/lib/python3.5/dist-packages/oslo_config/cfg.py", line 2640, in register_cli_opt
raise ArgsAlreadyParsedError("cannot register CLI option")
oslo_config.cfg.ArgsAlreadyParsedError: arguments already parsed: cannot register CLI option
How to Reproduce the Issue (as minimally as possible):
Re-run the genesis-full pipeline in CI/CD lab to start deployment from scratch
Any Additional Comments:
N.A.