diff options
author | Matthew Heon <matthew.heon@gmail.com> | 2018-02-14 09:51:24 -0500 |
---|---|---|
committer | Atomic Bot <atomic-devel@projectatomic.io> | 2018-02-15 15:47:59 +0000 |
commit | ce7a0171d156709bc8bbf2ac1138b8022bb08054 (patch) | |
tree | 0a4a4895770653cc13981949db0cfc27d1a35344 /test/build/http-context-subdir | |
parent | e814936915d28286fa88f1211bc354687a358a7c (diff) | |
download | podman-ce7a0171d156709bc8bbf2ac1138b8022bb08054.tar.gz podman-ce7a0171d156709bc8bbf2ac1138b8022bb08054.tar.bz2 podman-ce7a0171d156709bc8bbf2ac1138b8022bb08054.zip |
Squash logged errors from failed SQL rollbacks
Currently we unconditionally roll back transactions after error,
even if a commit has already been attempted. Commit is guaranteed
to end a transaction, though, whether by successfully committing
or by rolling back if that fails. As such, we attempt a double
rollback if a transaction fails at commit (for example, for a
constraint violation), which doesn't error but does log angry
warning messages. Ensure we don't try rolling back after commit
runs to prevent this.
Signed-off-by: Matthew Heon <matthew.heon@gmail.com>
Closes: #327
Approved by: rhatdan
Diffstat (limited to 'test/build/http-context-subdir')
0 files changed, 0 insertions, 0 deletions