-
Notifications
You must be signed in to change notification settings - Fork 24
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
Parsing layer blob: Broken pipe #657
Comments
@cgwalters , the problem came up again in MicroShift CI (see this log as an example). |
@cgwalters , our CI is in great pain because of this issue, is there a known workaround ? |
Not currently other than retrying, which we should probably add some defaults to do that... |
@cgwalters , this problem is causing a lot of grief in MicroShift CI. It's all over either booting VMs, or even running tests that pull a new layer. Is there a chance we add the retry w/a sooner than later in CentOS 9 and also backport it to RHEL 9.4? Once implementer, we should immediatelly provide feedback whether it made a difference. |
This one is like my enemy! I have a tracker over here for it coreos/rpm-ostree#4567 too
Discoveries so far:
More generally it's definitely a race condition; I can sometimes reproduce this by doing
ostree refs --delete ostree/container
and then re-running the rebase.Also of note: kola defaults to a uniprocessor VM, which I think is more likely to expose this race.
I'm quite certain it has something to do with the scheduling of us closing the pipe vs calling
FinishPipe
.The text was updated successfully, but these errors were encountered: