-
Notifications
You must be signed in to change notification settings - Fork 144
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
tmt cannot run tests on Fedora CoreOS containers #2884
Comments
@psss @lukaszachy @thrix I'd like to know whether this is something we might ignore for now. I'm working on extending https://github.com/teemtee/tmt/tree/main/tests/prepare/install to cover more distros, because of the recent It does not seem to be a regression, I'm wondering whether it's a known issue and whether I can therefore comment out those tests for Fedora CoreOS for now, and get back to them later once we fix the problem of running tests. |
I'd ignore it for now, definitely not a know issue to me though. |
But I'm not sure what is the right thing to do wrt usrlocal. Should we bind it in provision/podman? |
Or is this more about supporting 'bootc' containers? The inspect shows image has Note: https://containers.github.io/bootc/filesystem.html#var documents a bit of this |
I am perfectly fine with ignoring it for the purpose of fixing rpm-ostree bug reported and fixing the test runner later.
No idea. I suppose that in real-life scenarios, such a container gets all the blanks filled by the orchestrator. And I have exactly zero knowledge about this particular kind of image, so I can only guess. I think tmt will need to provide some volumes when running such a container, but now I wouldn't dare to say which, how, and why. |
Reading #3161 (comment), maybe we could take another look at this? |
The
/usr/local
in the container is a symlink to/var/uslocal
which does not exist. Therefore tmt fails scripts like/usr/local/bin/tmt-abort
.The text was updated successfully, but these errors were encountered: