sqlite: Rolling back transaction: transaction has already been committed or rolled back

[edsantiago]

Seen just now on debian rootless:

[+0879s] • [FAILED] [7.464 seconds]
         TOP-LEVEL [AfterEach]
         /var/tmp/go/src/github.com[/containers/podman/test/e2e/common_test.go:119](https://github.com/containers/podman/blob/c70572bcc20464c3c24547948ce463d4b875ae6e/test/e2e/common_test.go#L119)
           Podman play kube
           /var/tmp/go/src/github.com[/containers/podman/test/e2e/play_kube_test.go:2044](https://github.com/containers/podman/blob/c70572bcc20464c3c24547948ce463d4b875ae6e/test/e2e/play_kube_test.go#L2044)
             podman play kube multi doc yaml with multiple services, pods and deployments
.....
→ Enter [AfterEach] TOP-LEVEL - /var/tmp/go/src/github.com[/containers/podman/test/e2e/common_test.go:119](https://github.com/containers/podman/blob/c70572bcc20464c3c24547948ce463d4b875ae6e/test/e2e/common_test.go#L119) @ 08/14/23 20:41:46.799
           $ podman [options] stop --all -t 0
           time="2023-08-14T20:41:47Z" level=error msg="Rolling back transaction to save container 12e81790f5e72951d64e912a8094ad1411519d072cf2a14775ac95cec40ac185 state: sql: transaction has already been committed or rolled back"
           0250956f703a4a5167fc0a215d1603f26aeb390a511fb0c51d858955a855f8c5
           8a5d6bddf3bed10e2cfb8f4285b38b7e0d7ec9736818627b2930e8d9087b7619
           a1b9429341f0182dc5ea2e5f8beb28e8af1172b2fc5f226b6ccf717d4e2b911e
           bd36a78116b5f838aa46316dd01bd591221e577e89f2c6ec154eeaa29a92981a
           61a9b73d483cd02798c6f0bde422e1e9edb98ffc2d35a895fb2b51d861bb6961
           65a83457fc563bedf3557f477bbeb98ee5064519e7c2961cf690f5da8e6208c3
           7b732160254bd7c8cb05e06921433689a2c570abb8ecf25d22397bc58b7602d7
           Error: unmounting container 12e81790f5e72951d64e912a8094ad1411519d072cf2a14775ac95cec40ac185 storage: unmounting container 12e81790f5e72951d64e912a8094ad1411519d072cf2a14775ac95cec40ac185: saving container 12e81790f5e72951d64e912a8094ad1411519d072cf2a14775ac95cec40ac185 state: committing container 12e81790f5e72951d64e912a8094ad1411519d072cf2a14775ac95cec40ac185 state: disk I/O error
           $ podman [options] pod rm -fa -t 0
           time="2023-08-14T20:41:48Z" level=error msg="Storage for container 12e81790f5e72951d64e912a8094ad1411519d072cf2a14775ac95cec40ac185 has been removed"
           d5dd40c61ee001bd52e079b63a0e4c2f1f4944a4915a49c093b0720e3ff62cf0
           f903bd2d96951c54e36c23448ab44725a7b42731e02af0bd6b65342393701eda
           d6978a24ed4859b647b0f134701043d88e866650d9225ecd82904946630f8d4e
           c4b0adc5b396987ba30c47b8d97e6cb2fe3710d68725efe0ce9f625c990aef23
           $ podman [options] rm -fa -t 0

           [FAILED] command: [/var/tmp/go/src/github.com/containers/podman/bin/podman --storage-opt vfs.imagestore=/tmp/ginkgo3464613544/imagecachedir --root /tmp/podman_test4142766457/root --runroot /tmp/podman_test4142766457/runroot --runtime runc --conmon /usr/bin/conmon --network-config-dir /tmp/podman_test4142766457/root/etc/networks --network-backend netavark --cgroup-manager cgroupfs --tmpdir /tmp/podman_test4142766457 --events-backend file --db-backend sqlite --storage-driver vfs stop --all -t 0]
           stdout: 0250956f703a4a5167fc0a215d1603f26aeb390a511fb0c51d858955a855f8c5 8a5d6bddf3bed10e2cfb8f4285b38b7e0d7ec9736818627b2930e8d9087b7619 a1b9429341f0182dc5ea2e5f8beb28e8af1172b2fc5f226b6ccf717d4e2b911e bd36a78116b5f838aa46316dd01bd591221e577e89f2c6ec154eeaa29a92981a 61a9b73d483cd02798c6f0bde422e1e9edb98ffc2d35a895fb2b51d861bb6961 65a83457fc563bedf3557f477bbeb98ee5064519e7c2961cf690f5da8e6208c3 7b732160254bd7c8cb05e06921433689a2c570abb8ecf25d22397bc58b7602d7
           stderr: time="2023-08-14T20:41:47Z" level=error msg="Rolling back transaction to save container 12e81790f5e72951d64e912a8094ad1411519d072cf2a14775ac95cec40ac185 state: sql: transaction has already been committed or rolled back" Error: unmounting container 12e81790f5e72951d64e912a8094ad1411519d072cf2a14775ac95cec40ac185 storage: unmounting container 12e81790f5e72951d64e912a8094ad1411519d072cf2a14775ac95cec40ac185: saving container 12e81790f5e72951d64e912a8094ad1411519d072cf2a14775ac95cec40ac185 state: committing container 12e81790f5e72951d64e912a8094ad1411519d072cf2a14775ac95cec40ac185 state: disk I/O error

This is a new one to me. I'm not too concerned, because of the "disk I/O error" which is also new to me (not present anywhere else in my logs). However, this merits an issue just in case.

[github-actions]

A friendly reminder that this issue had no activity for 30 days.

[edsantiago]

No recurrence seen. As a software person, it is my prerogative to chalk this up to broken hardware.