LXD not getting IP address, MAAS 2.2b3 throwing django.db.utils.IntegrityError and AssertionError
Bug #1673204 reported by
Krzysztof Klimonda
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| MAAS |
Fix Released
|
Critical
|
Gavin Panella | ||
Bug Description
It's a brand-new MAAS 2.2b3 installation, and I'm deploying OpenStack cluster with Juju. It just threw django.
Related branches
lp:~allenap/maas/retry-context-not-active
- Blake Rouse (community): Approve
-
Diff: 173 lines (+90/-19)3 files modifiedsrc/maasserver/utils/orm.py (+1/-0)
src/maasserver/utils/tests/test_views.py (+63/-0)
src/maasserver/utils/views.py (+26/-19)
Revision history for this message
| Krzysztof Klimonda (kklimonda) wrote | #1 |
| Changed in maas: | |
| status: | New → In Progress |
| importance: | Undecided → Critical |
| assignee: | nobody → Gavin Panella (allenap) |
Revision history for this message
| Gavin Panella (allenap) wrote | #2 |
| Changed in maas: | |
| status: | In Progress → Fix Committed |
| Changed in maas: | |
| status: | Fix Committed → Fix Released |
To post a comment you must log in.
I've been puzzled by the "Retry context not active" failures... until I remembered that we have a separate transactional retry arrangement for web requests. It's composed of the same parts but ended up quite a lot more convoluted because Django says it understands transactions but doesn't really, and its web request machinery is not composed in a way that makes it easy to teach it. Anyway, when I added the retry stack in m.utils.orm I forgot about the web request code — my sanity trying to protect itself — and I didn't add the retry stack there. Time to fix that.