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

race: remote,rootless: podman network create followed by run #7808

Closed
edsantiago opened this issue Sep 28, 2020 · 8 comments
Closed

race: remote,rootless: podman network create followed by run #7808

edsantiago opened this issue Sep 28, 2020 · 8 comments
Labels
flakes Flakes from Continuous Integration kind/bug Categorizes issue or PR as related to a bug. kind/test-flake Categorizes issue or PR as related to test flakes. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. remote Problem is in podman-remote rootless stale-issue

Comments

@edsantiago
Copy link
Member

I've seen this one twice so far:

$ podman-remote network create --subnet 172.16.206.0/24 testnet-TrgvHhKQAK
/etc/cni/net.d/testnet-TrgvHhKQAK.conflist
$ podman-remote run --rm --network testnet-TrgvHhKQAK quay.io/libpod/testimage:20200917 ip a
Error: error preparing container 8efdbe7260f5e082c2a256ee0781a23fecbcd0776d5ac1b43d924d39cfae5086 for attach: error configuring network namespace for container 8efdbe7260f5e082c2a256ee0781a23fecbcd0776d5ac1b43d924d39cfae5086: CNI network "testnet-TrgvHhKQAK" not found
[ rc=127 (** EXPECTED 0 **) ]

Log: from PR 7803, ubuntu remote

Again, I'm not going to spend any time right now trying to reproduce (acting on the assumption that this will be an easy one to track down). I will try to keep track of flake occurrences and log them here.

@edsantiago edsantiago added flakes Flakes from Continuous Integration kind/bug Categorizes issue or PR as related to a bug. remote Problem is in podman-remote labels Sep 28, 2020
@edsantiago
Copy link
Member Author

I wonder if the race is in CNI? And I wonder if this is related? It's a very frequent flake in podman network rm, the classic symptom being:

Running: podman [options] network ls --quiet
podman-integrationtest
Running: podman [options] network rm podman-integrationtest
podman-integrationtest
Running: podman [options] network ls --quiet
podman-integrationtest
remove /home/some18764dude/.config/cni/net.d/eaac2f093ac23f24b699d68d1118f986b8620b03e3d5974e14c12147e06dfdab.conflist: no such file or directory

Recent instances (all one-offs, no triplets which cause a complete CI abort):

Podman network [It] podman network rm

Apologies in advance if this is unrelated.

@Luap99
Copy link
Member

Luap99 commented Sep 29, 2020

@edsantiago The tests are run in parallel, right?

@edsantiago
Copy link
Member Author

@Luap99 I cannot answer that with confidence, but yes, I believe so.

@baude
Copy link
Member

baude commented Sep 29, 2020

correct. in parallel depending on the run itself. i think remote tests are not in parallel.

@rhatdan rhatdan added the kind/test-flake Categorizes issue or PR as related to test flakes. label Oct 7, 2020
@github-actions
Copy link

github-actions bot commented Nov 7, 2020

A friendly reminder that this issue had no activity for 30 days.

@rhatdan
Copy link
Member

rhatdan commented Nov 7, 2020

@edsantiago @Luap99 Is this still an issue?

@edsantiago
Copy link
Member Author

The last two incidents reported by cirrus-flake-summarize are on 09-29:

@rhatdan
Copy link
Member

rhatdan commented Nov 10, 2020

Ok I will close this issue, with a hope and a prayer that it has been fixed, reopen if it happens again.

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
flakes Flakes from Continuous Integration kind/bug Categorizes issue or PR as related to a bug. kind/test-flake Categorizes issue or PR as related to test flakes. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. remote Problem is in podman-remote rootless stale-issue
Projects
None yet
Development

No branches or pull requests

5 participants