Skip to content

Conversation

@ricardobranco777
Copy link
Contributor

Skip some volume tests that fail on runc since opencontainers/runc#3990

https://openqa.opensuse.org/tests/5277891/file/podman_e2e-remoteintegration.txt

Failing tests:

  Running: /usr/bin/podman --storage-opt overlay.imagestore=/tmp/podman-e2e-3709866078/imagecachedir --root /tmp/podman-e2e-3709866078/subtest-1450834488/p/root --runroot /tmp/podman-e2e-3709
866078/subtest-1450834488/p/runroot --runtime runc --conmon /usr/bin/conmon --network-config-dir /etc/containers/networks --network-backend netavark --cgroup-manager systemd --tmpdir /tmp/pod
man-e2e-3709866078/subtest-1450834488/p --events-backend file --db-backend sqlite --storage-driver overlay run --rm -v testvol3:/etc/apk:copy quay.io/libpod/alpine:latest stat -c %h /etc/apk/
arch
  Error: OCI runtime error: runc: runc create failed: invalid mount &{Source:/tmp/podman-e2e-3709866078/subtest-1450834488/p/root/volumes/testvol3/_data Destination:/etc/apk Device:bind Flags
:20486 ClearedFlags:0 PropagationFlags:[278528] Data:copy Relabel: RecAttr:<nil> Extensions:0 IDMapping:<nil>}: bind mounts cannot have any filesystem-specific options applied
  [FAILED] Command failed with exit status 126. See above for error message.
  In [It] at: /root/podman/test/e2e/run_volume_test.go:452 @ 08/30/25 12:09:55.31
  [It] podman run with --mount and named volume with driver-opts
  /root/podman/test/e2e/run_volume_test.go:859

  Timeline >>
  > Enter [BeforeEach] TOP-LEVEL - /root/podman/test/e2e/common_test.go:117 @ 08/30/25 12:09:56.76
  < Exit [BeforeEach] TOP-LEVEL - /root/podman/test/e2e/common_test.go:117 @ 08/30/25 12:09:56.761 (0s)
  > Enter [It] podman run with --mount and named volume with driver-opts - /root/podman/test/e2e/run_volume_test.go:859 @ 08/30/25 12:09:56.761
  Running: /usr/bin/podman --storage-opt overlay.imagestore=/tmp/podman-e2e-3709866078/imagecachedir --root /tmp/podman-e2e-3709866078/subtest-369483378/p/root --runroot /tmp/podman-e2e-37098
66078/subtest-369483378/p/runroot --runtime runc --conmon /usr/bin/conmon --network-config-dir /etc/containers/networks --network-backend netavark --cgroup-manager systemd --tmpdir /tmp/podma
n-e2e-3709866078/subtest-369483378/p --events-backend file --db-backend sqlite --storage-driver overlay run --rm --mount type=volume,source=test_vol,dst=/test,volume-opt=type=tmpfs,volume-opt
=device=tmpfs,volume-opt=o=nodev quay.io/libpod/alpine:latest echo hello
  Error: OCI runtime error: runc: runc create failed: invalid mount &{Source:/tmp/podman-e2e-3709866078/subtest-369483378/p/root/volumes/test_vol/_data Destination:/test Device:bind Flags:204
86 ClearedFlags:0 PropagationFlags:[278528] Data:volume-opt=type=tmpfs,volume-opt=type=tmpfs,volume-opt=device=tmpfs,volume-opt=device=tmpfs,volume-opt=o=nodev,volume-opt=o=nodev Relabel: Rec
Attr:<nil> Extensions:0 IDMapping:<nil>}: bind mounts cannot have any filesystem-specific options applied
  [FAILED] Command failed with exit status 126. See above for error message.
  In [It] at: /root/podman/test/e2e/run_volume_test.go:864 @ 08/30/25 12:09:56.976
None

Skip some volume tests that fail on runc since
opencontainers/runc#3990

Signed-off-by: Ricardo Branco <rbranco@suse.de>
@openshift-ci
Copy link
Contributor

openshift-ci bot commented Aug 30, 2025

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ricardobranco777
Once this PR has been reviewed and has the lgtm label, please assign luap99 for approval. For more information see the Code Review Process.

The full list of commands accepted by this bot can be found here.

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@Luap99
Copy link
Member

Luap99 commented Aug 30, 2025

This sounds like a podman bug that must be fixed within podman itself instead of skipping the tests

@ricardobranco777
Copy link
Contributor Author

This sounds like a podman bug that must be fixed within podman itself instead of skipping the tests

Alright, will open an issue then.

@ricardobranco777
Copy link
Contributor Author

This sounds like a podman bug that must be fixed within podman itself instead of skipping the tests

#26938

@stale-locking-app stale-locking-app bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Nov 29, 2025
@stale-locking-app stale-locking-app bot locked as resolved and limited conversation to collaborators Nov 29, 2025
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. release-note-none

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants