When I delete a device I get an
"Error: Transaction managed block ended with pending COMMIT/ROLLBACK"
The device is deleted, but the error message (in red) is noisy and confusing.
NAV 3.9.3 postgresql-client-8.4.8 postgresql-server-8.4.8_1
--Ingeborg
On Fri, 16 Dec 2011 09:55:56 +0100 Ingeborg Hellemo ingeborg.hellemo@uit.no wrote:
When I delete a device I get an
"Error: Transaction managed block ended with pending COMMIT/ROLLBACK"
The device is deleted, but the error message (in red) is noisy and confusing.
Is there a Python traceback on the page, or just a plain error message above the IP Device list? If no traceback on the page, is there a traceback in your Apache error log?
morten.brekkevold@uninett.no said:
Is there a Python traceback on the page,
No.
morten.brekkevold@uninett.no said:
or just a plain error message above the IP Device list?
Yes. In red letters.
Actually, when I see the error I am still on <https://nav.uit.no/seeddb/netbox/
with my device listed (and checkbox crossed) and the "Confirm delete"-button
still in place.
If I then press "Confirm delete" once more I get "Error: syntax error at or near ")" LINE 1: DELETE FROM "netbox" WHERE "netboxid" IN () ^ " because the device was deleted the first time.
morten.brekkevold@uninett.no said:
If no traceback on the page, is there a traceback in your Apache error log?
Nothing.
Sorry ;-)
--Ingeborg
On Tue, 20 Dec 2011 12:46:49 +0100 Ingeborg Hellemo ingeborg.hellemo@uit.no wrote:
Actually, when I see the error I am still on <https://nav.uit.no/seeddb/netbox/
with my device listed (and checkbox crossed) and the "Confirm delete"-button
still in place.
If I then press "Confirm delete" once more I get "Error: syntax error at or near ")" LINE 1: DELETE FROM "netbox" WHERE "netboxid" IN () ^ " because the device was deleted the first time.
I did some checking, and just as in the alert profile issue you reported in LP#906850 it appears this is Django-version related.
I'm unable to reproduce the problem under Django 1.2, which we use for testing and development, but with Django 1.3 the problem readily appears.
I suggest you report it as a Django 1.3 incompatibility issue in the bugtracker.
-
Ingeborg Hellemo -
Morten Brekkevold