error handling of ml2 update-port on backend failure

Bug #1563162 reported by Kengo Hobo
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
networking-midonet
In Progress
Low
Kengo Hobo

Bug Description

error handling of ml2 update-port on backend failure.

update-port don't recover from the backend failures.
 e.g. fixed_ips

to avoid inconsistency between neutron and backend,
mark the resource ERROR.

Kengo Hobo (hobo-kengo)
Changed in networking-midonet:
assignee: nobody → Kengo Hobo (hobo-kengo)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to networking-midonet (master)

Fix proposed to branch: master
Review: https://review.openstack.org/298502

Changed in networking-midonet:
status: New → In Progress
Changed in networking-midonet:
importance: Undecided → Low
milestone: none → 2.0.0
Changed in networking-midonet:
milestone: 2.0.0 → 3.0.0
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on networking-midonet (master)

Change abandoned by Armando Migliaccio (<email address hidden>) on branch: master
Review: https://review.openstack.org/298502
Reason: This review is > 4 weeks without comment, and failed Jenkins the last time it was checked. We are abandoning this for now. Feel free to reactivate the review by pressing the restore button and leaving a 'recheck' comment to get fresh test results.

Changed in networking-midonet:
milestone: 3.0.0 → 4.0.0
Changed in networking-midonet:
milestone: 4.0.0 → 5.0.0
tags: added: newton-backport-potential ocata-backport-potential
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.