[release-1.40] tests: remove dependencies on online apt repositories#6835
[release-1.40] tests: remove dependencies on online apt repositories#6835nalind wants to merge 1 commit into
Conversation
Rework places to avoid installing packages using apt as part of tests. Use ubi10 where we need to be able to call setcap, setfattr, and getfattr from the same image. Signed-off-by: Nalin Dahyabhai <nalin@redhat.com>
dosubot
Bot
added
the
size:XS
nalind
changed the title
lsm5
left a comment
lsm5
left a comment
There was a problem hiding this comment.
TF jobs fail on not finding grpcnoop and passwd. Probably not worth blocking over until the move away from Cirrus.
Neither of those exist on this branch, and moving from Cirrus to something else isn't going to change that. |
|
Am I reading https://dashboard.packit.dev/jobs/testing-farm/1535319 right? That it's building packages off of the PR for the Copr Build(s), and then installing packages built from the main branch and running the tests that are in that package using the binaries from that package, using the TMT configuration (tests/tmt directory) from this PR? If so, what is that supposed to be verifying? |
|
ugh, yes, the buildah rpm is fetched from podman-next, which is to blame. Thanks @nalind . And that's because of the super-high Epoch of podman-next packages. So we can ignore all testing-farm jobs here. Should be fixed when the packit and TMT config is changed. |
|
If it's known that they're going to fail, can we remove them from older branches until that's resolved? |
sure thing. on it.. |
|
A friendly reminder that this PR had no activity for 30 days. |
2 participants
What type of PR is this?
/kind failing-test
What this PR does / why we need it:
Rework places to avoid installing packages using apt as part of tests. Use ubi10 where we need to be able to call setcap, setfattr, and getfattr from the same image.
How to verify it
Updated integration tests!
Which issue(s) this PR fixes:
None
Special notes for your reviewer:
Manual cherry pick from #6834.
Does this PR introduce a user-facing change?