DBDuplicateEntry not being handled when updating/creating Ports with the same address
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Ironic |
Fix Released
|
High
|
Lucas Alvares Gomes |
Bug Description
We should handle the DBDuplicateEntry at the db level and return a custom message to the internals from the error.
OUTPUT:
{{{
Server-side error: "(IntegrityError) column address is not unique u'UPDATE ports SET updated_at=?, address=? WHERE ports.id = ?' ('2013-12-04 10:01:59.664396', u'BB:BB:
Traceback (most recent call last):
File "/home/
result = f(self, *args, **kwargs)
File "ironic/
rpc_port.save()
File "ironic/
return fn(self, ctxt, *args, **kwargs)
File "ironic/
self.
File "ironic/
result = fn(*args, **kwargs)
File "ironic/
ref.
File "/home/
self.commit()
File "/home/
self.
File "/home/
self.
File "ironic/
_raise_
File "ironic/
raise exception.
DBDuplicateEntry: (IntegrityError) column address is not unique u'UPDATE ports SET updated_at=?, address=? WHERE ports.id = ?' ('2013-12-04 10:01:59.664396', u'BB:BB:
}}}
Changed in ironic: | |
assignee: | nobody → Lucas Alvares Gomes (lucasagomes) |
description: | updated |
summary: |
- DBDuplicateEntry not being handled when updating resources + DBDuplicateEntry not being handled when updating/creating Ports with the + same address |
description: | updated |
description: | updated |
Changed in ironic: | |
importance: | Undecided → High |
Changed in ironic: | |
milestone: | none → icehouse-2 |
status: | Fix Committed → Fix Released |
Changed in ironic: | |
milestone: | icehouse-2 → 2014.1 |
Fix proposed to branch: master /review. openstack. org/59955
Review: https:/