Failures in db_pool code: 'NoneType' object has no attribute '_keymap' or not returning rows.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Fix Released
|
High
|
Brian Lamar | ||
Diablo |
Fix Released
|
Undecided
|
Unassigned | ||
nova (Ubuntu) |
Fix Released
|
High
|
Unassigned | ||
Oneiric |
Won't Fix
|
High
|
Unassigned | ||
Precise |
Fix Released
|
High
|
Unassigned |
Bug Description
Running rev 1514, getting this on instance build in XenServer.
2011-09-01 02:38:04,374 ERROR nova.rpc [-] Exception during message handling
(nova.rpc): TRACE: Traceback (most recent call last):
(nova.rpc): TRACE: File "/usr/lib/
(nova.rpc): TRACE: rval = node_func(
(nova.rpc): TRACE: File "/usr/lib/
(nova.rpc): TRACE: return f(*args, **kw)
(nova.rpc): TRACE: File "/usr/lib/
(nova.rpc): TRACE: self._run_
(nova.rpc): TRACE: File "/usr/lib/
(nova.rpc): TRACE: requested_
(nova.rpc): TRACE: File "/usr/lib/
(nova.rpc): TRACE: 'args': args})
(nova.rpc): TRACE: File "/usr/lib/
(nova.rpc): TRACE: return get_impl(
(nova.rpc): TRACE: File "/usr/lib/
(nova.rpc): TRACE: rv = list(rv)
(nova.rpc): TRACE: File "/usr/lib/
(nova.rpc): TRACE: raise result
(nova.rpc): TRACE: RemoteError: AttributeError 'NoneType' object has no attribute '_keymap'
(nova.rpc): TRACE: [u'Traceback (most recent call last):\n', u' File "/usr/lib/
(nova.rpc): TRACE:
Related branches
- Chuck Short (community): Approve
-
Diff: 116 lines (+96/-0)3 files modifieddebian/changelog (+6/-0)
debian/patches/fix-lp838581-removed-db_pool-complexities.patch (+89/-0)
debian/patches/series (+1/-0)
Changed in nova: | |
assignee: | nobody → Brian Lamar (blamar) |
Changed in nova: | |
importance: | Undecided → High |
status: | New → In Progress |
summary: |
- 'NoneType' object has no attribute '_keymap' on xenserver instance build + 'NoneType' object has no attribute '_keymap' |
summary: |
- 'NoneType' object has no attribute '_keymap' + Failures in db_pool code: 'NoneType' object has no attribute '_keymap' + or not returning rows. |
tags: | added: diablo-backport |
Changed in nova: | |
status: | In Progress → Fix Committed |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
status: | Fix Released → Fix Committed |
Changed in nova (Ubuntu): | |
importance: | Undecided → High |
status: | New → Confirmed |
milestone: | none → ubuntu-11.10 |
tags: | added: server-o-rs |
Changed in nova (Ubuntu Precise): | |
milestone: | none → precise-alpha-1 |
Changed in nova (Ubuntu Oneiric): | |
importance: | Undecided → High |
milestone: | none → oneiric-updates |
Changed in nova: | |
milestone: | none → essex-1 |
tags: | removed: diablo-backport |
Changed in nova: | |
status: | Fix Committed → Fix Released |
Changed in nova: | |
milestone: | essex-1 → 2012.1 |
My suspicion here is that fixed_ip_ associate_ pool is failing when being called in quick succession aka at the 'same time'. I believe this is what "with_lockmode" is supposed to prevent...but the SQLAlchemy documentation is very poor in this area.
We're using InnoDB tables are being used.