Skip to content
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

[CI/CD] build-package (deb) is broken #31443

Closed
songy23 opened this issue Feb 27, 2024 · 3 comments · Fixed by #31527
Closed

[CI/CD] build-package (deb) is broken #31443

songy23 opened this issue Feb 27, 2024 · 3 comments · Fixed by #31527
Labels
bug Something isn't working ci-cd CI, CD, testing, build issues

Comments

@songy23
Copy link
Member

songy23 commented Feb 27, 2024

Component(s)

No response

Describe the issue you're reporting

See recent failures https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/8065610224/job/22032135180?pr=31421, https://github.com/open-telemetry/opentelemetry-collector-contrib/actions/runs/8065600280/job/22032028700

# test install
echo
podman run --name $container_name -d $image_name

Error: OCI runtime error: chmod `run/shm`: Operation not supported
podman rm -fv otelcontribcol-deb-test >/dev/null 2>&1 || true
Error: Process completed with exit code 126.
@songy23 songy23 added ci-cd CI, CD, testing, build issues needs triage New item requiring triage labels Feb 27, 2024
@crobert-1
Copy link
Member

Looks like this is containers/crun#1308. The workaround for now may have to be manually downloading the fixed crun package and updating the path for podman. Workaround reference.

@cwegener
Copy link
Contributor

cwegener commented Mar 1, 2024

Oh. Awesome. My change to podman worked and errors are now easier to resolve by everyone. 😄

Interesting how this error only started occurring recently ... must have been a change in Kernel version in the GH runner image?

This also reminds me of open-telemetry/opentelemetry-collector-releases#623 I'll put a PR together for it.

@cwegener
Copy link
Contributor

cwegener commented Mar 2, 2024

Quick root cause: the runner image kernel upgrade from 6.2.0-1019-azure to 6.5.0-1015-azure likely introduced the regression (likely because of the regression from linux 6.6 being backported to 6.5 and included in the 6.5 azure kernel from Canonical/Microsoft). https://github.com/actions/runner-images/releases/tag/ubuntu22%2F20240225.1

And yeah, the crun fix from the containers community probably was not possible to be backported to the old crun codebase that ships with ubuntu 22.04? containers/crun@be16ee7

I think this should be a bug ticket with the actions/runner-images repo.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working ci-cd CI, CD, testing, build issues
Projects
None yet
Development

Successfully merging a pull request may close this issue.

3 participants