diff options
| author | Paul Holzinger <pholzing@redhat.com> | 2022-03-28 20:55:29 +0200 |
|---|---|---|
| committer | Matthew Heon <mheon@redhat.com> | 2022-03-30 15:36:05 -0400 |
| commit | c1d9851a4f290b641a092a0f46af898c75587f0f (patch) | |
| tree | afcfe22c583339fdaf6375881fdb0253725143ce /libpod/networking_linux.go | |
| parent | a4203bd66cf802449cf9dda9498efa83fa0302e8 (diff) | |
| download | podman-c1d9851a4f290b641a092a0f46af898c75587f0f.tar.gz podman-c1d9851a4f290b641a092a0f46af898c75587f0f.tar.bz2 podman-c1d9851a4f290b641a092a0f46af898c75587f0f.zip | |
upgrade tests: fix networking problems
With podman4 we support netavark, however old versions will still use
cni. Since netavark and cni can conflict we should not mix them.
Remove the network setup from the inital podman command and create the
directories manually to prevent such conflicts.
Also the update to 4.0 changes the network db structure. While it is
compatible from 3.X to 4.0 it will fail the other way around. In this
test it will happen because the cleanup process still uses the old
podman while the network connect/disconnect test already changed the db
format. Therefore the cleanup process cannot see any networks and will
not tear it down. The following start will fail because the ip address
is already assigned.
Fixes #13679
Signed-off-by: Paul Holzinger <pholzing@redhat.com>
Diffstat (limited to 'libpod/networking_linux.go')
0 files changed, 0 insertions, 0 deletions