Devstack tacker installtion fails

[Janki Chhatbar]

I am installing Tacker Devstack (master). The installtion fials with following error.

File "/opt/stack/tacker/tacker/api/v1/resource.py", line 89, in resource
  result = method(request=request, **args)
File "/opt/stack/tacker/tacker/api/v1/base.py", line 394, in create
  obj = obj_creator(request.context, **kwargs)
File "/opt/stack/tacker/tacker/common/log.py", line 33, in wrapper
  return method(*args, **kwargs)
File "/opt/stack/tacker/tacker/nfvo/nfvo_plugin.py", line 67, in create_vim
  vim_id=vim_obj['id'])
File "/opt/stack/tacker/tacker/openstack/common/excutils.py", line 82, in __exit__
  six.reraise(self.type_, self.value, self.tb)
File "/opt/stack/tacker/tacker/nfvo/nfvo_plugin.py", line 61, in create_vim
  self._vim_drivers.invoke(vim_type, 'register_vim', vim_obj=vim_obj)
File "/opt/stack/tacker/tacker/common/driver_manager.py", line 70, in invoke
  return getattr(driver, method_name)(**kwargs)
File "/opt/stack/tacker/tacker/common/log.py", line 33, in wrapper
  return method(*args, **kwargs)
File "/opt/stack/tacker/tacker/nfvo/drivers/vim/openstack_driver.py", line 140, in register_vim
  ks_client = self.authenticate_vim(vim_obj)
File "/opt/stack/tacker/tacker/nfvo/drivers/vim/openstack_driver.py", line 66, in authenticate_vim
  keystone_version = self._validate_auth_url(auth_url)
File "/opt/stack/tacker/tacker/nfvo/drivers/vim/openstack_driver.py", line 94, in _validate_auth_url
  raise nfvo.VimConnectionException(message=e.message)
VimConnectionException: Discovery of client versions failed.

I am attaching the log file and local.conf file

[Janki Chhatbar (jankihchhatbar)]

The issue was of proxy. Because of proxy, tacker could not get keystoneclient version. This threw the above exception. The solution is to add "no_proxy" for the devstack machine IP in .bashrc file.

[Sridhar Ramaswamy (srics-r)]

This is not a bug. Reliable connection to keystone service is required through the life of the tacker-service. There is nothing to fix IMO other than, perhaps we can document this dependency somewhere in our Install / Deployer Guide.