Comment 8 for bug 2069365
Revision history for this message
| John A Meinel (jameinel) wrote Re: [Bug 2069365] Re: [doc] create a production troubleshooting guide for "state changing too quickly" | #8 |
© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
0f7b58d
(Get the code!)
I'd be ok with reporting more on failed assertions, but it is fairly likely
to not quite give enough context. The basic form of the assertion is "a
document of this shape exists/doesn't exist". So you might put in a thing
that says "the field foo has the value 'bar'", and all we know is that we
are unable to query for a document that has the value 'bar'. It may be that
the document doesn't exist at all. It may be that the document exists but
has the value "bing". It may be that the document exists but doesn't have
the field, etc.
In general, if you get "state changing too quickly" it is almost always a
"poorly assessed transaction, that has a prerequisite that isn't being
checked correctly". And if we were checking it correctly, then you'd be
getting a better error message. It isn't something that can be achieved
holistically.
Looking through:
https:/
The first issue appears to be a bug that we have addressed (during
migration if you had a model that was referenced multiple times, it could
cause a conflict.)
The `juju-debug-log` issues is more one of the framework's data itself
being inconsistent. (It clearly has a reference for an event, but that
events snapshot doesn't appear to exist.)