summaryrefslogtreecommitdiff
path: root/test/utils
diff options
context:
space:
mode:
authorChris Evich <cevich@redhat.com>2022-04-04 11:39:56 -0400
committerChris Evich <cevich@redhat.com>2022-04-21 14:29:44 -0400
commitc67d6a52c42c97b6b8f127eb66f21871058e36fa (patch)
treea6f74f9d53f75ffd96dfd1b5484c86073ca55e3c /test/utils
parentcb09c26c6519c2fff8be7285d585672a9066f2da (diff)
downloadpodman-c67d6a52c42c97b6b8f127eb66f21871058e36fa.tar.gz
podman-c67d6a52c42c97b6b8f127eb66f21871058e36fa.tar.bz2
podman-c67d6a52c42c97b6b8f127eb66f21871058e36fa.zip
Fix using --network-backend on podman-remote
When this option was added to the e2e tests, there was no CI Automation support for running remote tests w/ netavark. When added, many e2e test errors/failures are generated due to this option not being valid for the remote client. Fix this in the tests by conditionally adding the option if the test is running the remote client. Signed-off-by: Chris Evich <cevich@redhat.com>
Diffstat (limited to 'test/utils')
-rw-r--r--test/utils/utils.go2
1 files changed, 1 insertions, 1 deletions
diff --git a/test/utils/utils.go b/test/utils/utils.go
index da56a3a2e..39a0ac875 100644
--- a/test/utils/utils.go
+++ b/test/utils/utils.go
@@ -110,7 +110,7 @@ func (p *PodmanTest) PodmanAsUserBase(args []string, uid, gid uint32, cwd string
}
runCmd := append(wrapper, podmanBinary)
- if p.NetworkBackend == Netavark {
+ if !p.RemoteTest && p.NetworkBackend == Netavark {
runCmd = append(runCmd, []string{"--network-backend", "netavark"}...)
}