Failing e2e tests #8309
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Comments
openshift-ci-robot
added
the
kind/bug
|
Thanks for reaching out! Could you share the entire log? I would expect an error message to appear before the ginkgo log. |
|
Logs are attached from |
|
Did you get this to repeat? This is about the most simple container on the system. I would figure this is a hiccup or all of your containers would be blowing up. |
|
Yeah. This happens every time. Have yet to get them to succeed. I'm on
Fedora 32 and have cgroups v1 and v2 enabled if that matters
…On Sat, Nov 14, 2020, 04:35 Daniel J Walsh ***@***.***> wrote:
Did you get this to repeat? This is about the most simple container on the
system. I would figure this is a hiccup or all of your containers would be
blowing up.
—
You are receiving this because you authored the thread.
Reply to this email directly, view it on GitHub
<#8309 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABTBOJ7CR6RXW6BPQK3Z5RTSPZTPXANCNFSM4TSV2QNQ>
.
|
|
Podman works with either v1 or v2, not sure if it works with both. |
|
Are you able to reproduce this error? I tried I'm not sure why specifically the integ tests are failing with |
|
This works fine on my F33 box. The log looks like something with firewall is blowing up on your machine? |
removing that network doesn't work. I see this error around. Any recommendations to fix it? |
|
Can you do |
|
Just tried it. Same problem. I just discovered that podman fails when running under |
|
I am pretty sure @mheon knows what to do :) |
|
Wow, I think that error is coming out of firewalld - I've never seen
anything like it before (which is probably not what you were hoping to
hear...). Best idea I have is stop all containers and do a firewall reload
to clear any potential leakage from failed test runs?
…On Wed, Nov 18, 2020, 05:24 Valentin Rothberg ***@***.***> wrote:
I am pretty sure @mheon <https://github.com/mheon> knows what to do :)
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#8309 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AB3AOCGTH6ZRHAFK7RCMNGLSQOOFZANCNFSM4TSV2QNQ>
.
|
|
Definitely not what I hoped to hear, but happy to help debug. Ran some of the commands from #5431. Looks like a completely separate issue from podman. Maybe a conflict with docker. |
|
I was able to fully reproduce the error on Fedora 33 using podman from the repos (ie. not built from source). Had to reboot because my wifi became non-functional, but podman still worked after this. Lesson learned, don't try developing docker competitors with docker installed. Docker will fight back |
github-actions
bot
added
the
locked - please file new issue/PR
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
/kind bug
Description
Make test is failing integ tests.
Steps to reproduce the issue:
make testDescribe the results you received:
Describe the results you expected:
Additional information you deem important (e.g. issue happens only occasionally):
Output of
podman version:Output of
podman info --debug:Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide?
This is recent master branch build and just trying to run the tests
The text was updated successfully, but these errors were encountered: