-
Notifications
You must be signed in to change notification settings - Fork 2.8k
Closed
Labels
flakesFlakes from Continuous IntegrationFlakes from Continuous Integrationkind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.locked - please file new issue/PRAssist humans wanting to comment on an old issue or PR with locked comments.Assist humans wanting to comment on an old issue or PR with locked comments.remoteProblem is in podman-remoteProblem is in podman-remote
Description
The following sequence is starting to fail frequently in CI:
# podman-remote network create a
# podman-remote network create b
# podman-remote run --network b something-something
Error: CNI network \"b\" not found"
Error: error configuring network namespace for container X: CNI network "b" not found
I cannot reproduce it on my f33 laptop, possibly because it's faster than the CI VMs. What I can reproduce easily is:
# ./bin/podman-remote network create b;./bin/podman-remote network rm b
and then, in the podman server window, I see:
ERRO[1299] Error loading CNI config list file /etc/cni/net.d/b.conflist: error reading /etc/cni/net.d/b.conflist: open /etc/cni/net.d/b.conflist: no such file or directory
(not 100% of the time, but about 25%)
master @ 6fbf73e
Podman network [It] podman network prune
- gce_instance:fedora : int remote fedora-33 root host
- gce_instance:prior-fedora : int remote fedora-32 root host
Metadata
Metadata
Assignees
Labels
flakesFlakes from Continuous IntegrationFlakes from Continuous Integrationkind/bugCategorizes issue or PR as related to a bug.Categorizes issue or PR as related to a bug.locked - please file new issue/PRAssist humans wanting to comment on an old issue or PR with locked comments.Assist humans wanting to comment on an old issue or PR with locked comments.remoteProblem is in podman-remoteProblem is in podman-remote