In current implementation, keys of 'chassis' in DF-DB are set and published by controllers. But when a controller runs, it doesn't initialize the publisher. That causes the 'chassis created' event can't be published correctly, and the remote lport process will also be wrong for the absent of tunnel to the chassis.
2016-08-27 12:25:07.916 ^[[00;32mDEBUG dragonflow.controller.df_local_controller [^[[00;36m-^[[00;32m] ^[[01;35m^[[00;32mPort 3b502e65-0b60-4147-8211-5ed79f5f1743 has not been bound or it is a vPort ^[[00m ^[[00;33mfrom (pid=2557) _logical_port_process /opt/stack/dragonflow/dragonflow/controller/df_local_controller.py:200^[[00m
2016-08-27 12:25:07.917 ^[[01;33mWARNING dragonflow.controller.df_local_controller [^[[00;36m-^[[01;33m] ^[[01;35m^[[01;33mNo tunnel for remote logical port {u'parent_name': None, u'binding_profile': None, u'tunnel_key': 8, u'macs': [u'fa:16:3e:26:0f:20'], u'name': u'', u'allowed_address_pairs': [], u'lswitch': u'4112132a-1776-4092-89ff-a758b05b50f8', u'enabled': True, u'topic': u'978b414989f24b1e84ea683d0ea1c7b3', u'ips': [u'10.0.0.9'], u'device_owner': u'compute:nova', u'chassis': u'ubuntu-5-6', u'version': 1, u'tag': None, u'subnets': [u'1e51a987-5348-4d62-8b42-6ae8ea97b99b'], u'port_security_enabled': True, u'binding_vnic_type': u'normal', u'id': u'f81bf17c-9462-4b2a-a8a0-6e1482620300', u'security_groups': [u'578acdb2-e154-4211-b945-2ebbb1e298ba'], u'device_id': u'ec6e6f35-0c89-4a7b-b859-65b3d855d381'}{'is_local': False, 'network_type': None, 'local_network_id': 3}^[[00m
2016-08-27 12:25:07.917 ^[[00;32mDEBUG dragonflow.controller.df_local_controller [^[[00;36m-^[[00;32m] ^[[01;35m^[[00;32mPort 764ff83d-6c45-49aa-a2e2-fceaf0f32aaa has not been bound or it is a vPort ^[[00m ^[[00;33mfrom (pid=2557) _logical_port_process /opt/stack/dragonflow/dragonflow/controller/df_local_controller.py:200^[[00m
Set to High, since I think this bug was already solved elsewhere.