Two things come to mind:

1) Have you defined "provider" as a flat network provider? 2) Most importantly, are all of the necessary environmental variables defined? For example, can you:

root@OpenStack:~# openstack network list
+--------------------------------------+---------+--------------------------------------+
| ID                                   | Name    | Subnets                              |
+--------------------------------------+---------+--------------------------------------+
| 7fe25645-1ab0-48e9-970d-f3887efa361a | private | aa332cea-358b-45b6-adc9-474803c995f8 |
| ff4bbe7c-50c8-436f-ba37-457f7d6238c1 | public  | 160c9ea4-c16f-46d4-8008-be31e530d683 |
+--------------------------------------+---------+--------------------------------------+

If not, you need to source a script that looks like this:

#!/usr/bin/env bash

# To use an OpenStack cloud you need to authenticate against the Identity
# service named keystone, which returns a **Token** and **Service Catalog**.
# The catalog contains the endpoints for all services the user/tenant has
# access to - such as Compute, Image Service, Identity, Object Storage, Block
# Storage, and Networking (code-named nova, glance, keystone, swift,
# cinder, and neutron).
#
# *NOTE*: Using the 2.0 *Identity API* does not necessarily mean any other
# OpenStack API is version 2.0. For example, your cloud provider may implement
# Image API v1.1, Block Storage API v2, and Compute API v2.0. OS_AUTH_URL is
# only for the Identity API served through keystone.
export OS_AUTH_URL=http://111.111.111.111:5000/v2.0

# With the addition of Keystone we have standardized on the term **tenant**
# as the entity that owns the resources.
export OS_TENANT_ID=
export OS_TENANT_NAME="admin"

# unsetting v3 items in case set
unset OS_PROJECT_ID
unset OS_PROJECT_NAME
unset OS_USER_DOMAIN_NAME

# In addition to the owning entity (tenant), OpenStack stores the entity
# performing the action as the **user**.
export OS_USERNAME="admin"

# With Keystone you pass the keystone password.
echo "Please enter your OpenStack Password: "
read -sr OS_PASSWORD_INPUT
export OS_PASSWORD=$OS_PASSWORD_INPUT

As i can see your linux bridge name must be ens160, is this bridge interface or ethernet interface? You must create the bridge with your distribution's tools and then you must define the bridge name in linuxbridge_agent.ini on [linux_bridge]\physical_interface_mappings = provider:<bridge_name>

The simplest topology is on bridge with one physical interface on it.

1 see log file : dhcp-agent.log linuxbridge-agent.log metadata-agent.log ......

2  openstack network agent list