When using the provider networks extension with the nicira plugin, a single, large, network might be backed by several NVP logical switches.
When reading the logical status for a port, the plugin invokes nvplib.get_logical_port_status. This routine reads a logica port configuraiton providing the logical switch uuid and the logica port uuid.
The Plugin leverages the fact that nvp logical switch uuid == quantum network id.
However, this is not always true in the case of extended switches. The operation then migth a 404 error if the port was being sought on the first logical switch of the chain, whereas it might be on a different logical switch. Its state is then set to ERROR whereas it should be 'ACTIVE' or 'DOWN'.
Steps to reproduce:
1) edit /etc/quantum/plugins/nicira/nvp.ini and set max_lp_per_bridged_ls to a small value, for instance 3
2) restart quantum-server
3) quantum net-create bridged --provider:network_type=vlan --provider:physical_network=9f5bd279-fcda-44c4-a709-efec63bc6eb9 --provider:segmentation_id=666
4) quantum subnet-create bridged 192.168.0.0/16
5) quantum port-create bridged --name bridged-2; quantum port-create bridged --name bridged-3
bridged-3 will be created on a 2nd logical switch (the 3rd port on the 1st ls is the dhcp port)
6) user@os-nvp-ctrl:~/devstack$ quantum port-show bridged-3
+-----------------------+------------------------------------------------------------------------------------+
| Field | Value |
+-----------------------+------------------------------------------------------------------------------------+
| admin_state_up | True |
| device_id | |
| device_owner | |
| fixed_ips | {"subnet_id": "1e568b32-198f-4ad3-8520-fa15555b2e89", "ip_address": "192.168.0.5"} |
| id | 691d2cbc-43c0-4c2c-b065-ff4d2f171fc9 |
| mac_address | fa:16:3e:a9:db:0e |
| name | bridged-3 |
| network_id | 6ec622d4-8608-40a7-8712-d7e9d96bda8c |
| port_security_enabled | True |
| security_groups | f0750245-e9e0-4a2f-87d0-89205bdb8773 |
| status | ERROR |
| tenant_id | d6ddcd5d5d6f4c30bdb7fd3407b4a4fa |
+-----------------------+------------------------------------------------------------------------------------+
Status should not be 'ERROR' but 'DOWN'
Fix proposed to branch: master
Review: https:/