taas can create tap-service on a port down but new rules not added even the port is up later

First,My openstack version is Queens.
We can reproduce the result as follows:

1.create a tap-service on a neutron port down, we can get the success result on the console

# neutron tap-service-create --name dst1 --port 7db38629-39b7-46f7-935c-46e74cdb2dbf
neutron CLI is deprecated and will be removed in the future. Use openstack CLI instead.
Created a new tap_service:
+-------------+--------------------------------------+
| Field | Value |
+-------------+--------------------------------------+
| description | |
| id | c1cf4617-cb26-44d0-9a74-d0c2f55aef41 |
| name | dst1 |
| port_id | 7db38629-39b7-46f7-935c-46e74cdb2dbf |
| project_id | 94b35ccc09164772a833e433b81c3e25 |
| status | ACTIVE |
| tenant_id | 94b35ccc09164772a833e433b81c3e25 |
+-------------+--------------------------------------+

notice: port 7db38629-39b7-46f7-935c-46e74cdb2dbf is down ,we can check its status using the following command;

#openstack port list | grep 7db38629-39b7-46f7-935c-46e74cdb2dbf
| 7db38629-39b7-46f7-935c-46e74cdb2dbf | s8 | fa:16:3e:37:5e:10 | ip_address='192.168.101.4', subnet_id='2b22fb1e-32fc-4782-ac64-f3d93f46f4cf' | DOWN |

2.bind the port 7db38629-39b7-46f7-935c-46e74cdb2dbf to a VM and start the VM,now check the status,the port is up:

#openstack port list | grep 7db38629-39b7-46f7-935c-46e74cdb2dbf
| 7db38629-39b7-46f7-935c-46e74cdb2dbf | s8 | fa:16:3e:37:5e:10 | ip_address='192.168.101.4', subnet_id='2b22fb1e-32fc-4782-ac64-f3d93f46f4cf' | ACTIVE |

3.After a while, Let's check the br-tap openflow rules,I do not see the rules configured by tap-service-create on br-tap, eg:
table=1,priority=1,dl_vlan=3900,actions=output:in_port
table=2,priority=1,dl_vlan=3900,output:patch_tap_int