VIM's status stucks at pending after registering

Hi ,

After installing tacker successfully on Ocata version, I did register a VIM but its status is pending.
# tacker vim-list
+--------------------------------------+----------------------------------+-------------+-----------+------------+------------------------------+---------+
| id | tenant_id | name | type | is_default | placement_attr | status |
+--------------------------------------+----------------------------------+-------------+-----------+------------+------------------------------+---------+
| 91be084e-52ba-4fbf-acd9-4967cac66e59 | ebce5bd3b8de43838f1cbf1d2551497b | default_VIM | openstack | False | {u'regions': [u'RegionOne']} | PENDING |
+--------------------------------------+----------------------------------+-------------+-----------+------------+------------------------------+---------+

 I installed mistral as well. Please help to take a look the below log from mistral log : https://hastebin.com/vorurabela.sql

-Tacker version:
 #tacker-server --version
Guru meditation now registers SIGUSR1 and SIGUSR2 by default for backward compatibility. SIGUSR1 will no longer be registered in a future release, so please use SIGUSR2 to generate reports.
%prog 0.7.1.dev203

-Starting tacker-server:
#python /usr/bin/tacker-server --config-file /usr/etc/tacker/tacker.conf --log-file /var/log/tacker/tacker.log
Guru meditation now registers SIGUSR1 and SIGUSR2 by default for backward compatibility. SIGUSR1 will no longer be registered in a future release, so please use SIGUSR2 to generate reports.

-Starting mistral:
 mistral-server --server api,engine,executor --config-file /etc/mistral/mistral.conf

|\\ //| || ||
||\\ //|| __ || __ __ ||
|| \\// || || // |||||| || \\ // \\ ||
|| \/ || \\ || || || \\ ||
|| || || \\ || || || /\\ ||
|| || || __// ||_// || \\__// \\_ ||
Mistral Workflow Service, version 5.0.0

Launching server components ['api', 'engine', 'executor']...
2017-08-24 12:27:05.474 196019 WARNING oslo_db.sqlalchemy.engines [-] URL mysql://root:***@localhost:3306/mistral does not contain a '+drivername' portion, and will make use of a default driver. A full dbname+drivername:// protocol is recommended. For MySQL, it is strongly recommended that mysql+pymysql:// be specified for maximum service compatibility
2017-08-24 12:27:05.754 196019 WARNING keystonemiddleware.auth_token [req-12a67ed7-7160-4ff6-881f-de1a7968f38d - - - - -] AuthToken middleware is set with keystone_authtoken.service_token_roles_required set to False. This is backwards compatible but deprecated behaviour. Please set this to True.
2017-08-24 12:27:05.755 196019 WARNING keystonemiddleware.auth_token [req-12a67ed7-7160-4ff6-881f-de1a7968f38d - - - - -] Use of the auth_admin_prefix, auth_host, auth_port, auth_protocol, identity_uri, admin_token, admin_user, admin_password, and admin_tenant_name configuration options was deprecated in the Mitaka release in favor of an auth_plugin and its related options. This class may be removed in a future release.
2017-08-24 12:27:05.762 196019 INFO oslo.service.wsgi [req-12a67ed7-7160-4ff6-881f-de1a7968f38d - - - - -] mistral_api listening on 0.0.0.0:8989
2017-08-24 12:27:05.762 196019 INFO oslo_service.service [req-12a67ed7-7160-4ff6-881f-de1a7968f38d - - - - -] Starting 32 workers
/usr/lib/python2.7/site-packages/oslo_messaging/server.py:341: FutureWarning: blocking executor is deprecated. Executor default will be removed. Use explicitly threading or eventlet instead in version 'pike' and will be removed in version 'rocky'
  category=FutureWarning)
Executor server started.
Engine server started.

Thanks,
Trung.