Neutron port-update fails to roll back the binding:profile data in ports table in neutron DB if a MechanismDriverError thrown by a mechanism driver
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
neutron |
Expired
|
Undecided
|
Unassigned |
Bug Description
Steps to reproduce:
1. Inherit the update_
2. Throw MechanismDriver
Expected output:
None of the updated port parameters should be added in DB for the ports table as well as ml2_port_bindings table.
Actual output:
Eventhough the MechanismDriver
Attached the logs in paste site:
http://
Neutron port-update REST API output:
Earlier neutron port was created with local_link_
sdn@IronicVM:
HTTP/1.1 500 Internal Server Error
Content-Type: application/json; charset=UTF-8
Content-Length: 108
X-Openstack-
Date: Fri, 15 Apr 2016 11:30:30 GMT
{"NeutronError": {"message": "update_
sdn@IronicVM:
sdn@IronicVM:
+------
| Field | Value |
+------
| admin_state_up | True |
| allowed_
| binding:host_id | baremetal |
| binding:profile | {"local_
| binding:vif_details | {} |
| binding:vif_type | unbound |
| binding:vnic_type | baremetal |
| device_id | |
| device_owner | |
| extra_dhcp_opts | |
| fixed_ips | |
| id | a3f10e8b-
| mac_address | fa:16:3e:60:c7:b8 |
| name | P1 |
| network_id | 5be51697-
| port_security_
| security_groups | e39e3b81-
| status | ACTIVE |
| tenant_id | fd415d61bf5c4ba
+------
Changed in neutron: | |
assignee: | nobody → Koteswara Rao Kelam (koti-kelam) |
Changed in neutron: | |
assignee: | Koteswara Rao Kelam (koti-kelam) → Phani Pawan (ppawan) |
This bug is > 240 days without activity. We are unsetting assignee and milestone and setting status to Incomplete in order to allow its expiry in 60 days.
If the bug is still valid, then update the bug status.