-
Notifications
You must be signed in to change notification settings - Fork 307
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
(process:10533): OSTree-CRITICAL **: ostree_repo_commit_transaction: assertion 'self->in_transaction == TRUE' failed #1196
Labels
Comments
Hmm...looking at the skopeo-ostree code I see that it's not calling |
Confirmed that going back to:
works, then causes the failure again. |
Starting some notes/patches in ostreedev/ostree-go#12 |
cgwalters
added a commit
to cgwalters/ostree
that referenced
this issue
Sep 21, 2017
Such an evil bug 🙈. I was just reading an strace trying to figure out what was going on, and noticed we had the `XXXXXX` in the lockfile name. It was only after that I realized that that this might *be* the cause of the skopeo issue. This is another case where we definitely need more test coverage of things that actually use the API multiple times in process; might look at dusting off the work for the rpm-ostree test. Closes: ostreedev#1196
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
In a recent FAHC compose (26.312), installing an
etcd
system container blew up and the trace seems to point toostree
The text was updated successfully, but these errors were encountered: