summaryrefslogtreecommitdiff
diff options
context:
space:
mode:
authorEd Santiago <santiago@redhat.com>2022-02-21 08:42:37 -0700
committerEd Santiago <santiago@redhat.com>2022-02-21 08:49:11 -0700
commitf018c07edfb4d83b7c97e98223a4a7a56fd12d8b (patch)
treea877aa3f3178b4ea9a057988d6636f54308e003e
parentd224a0f8ac4978c3ac399a0940f785892d63daa8 (diff)
downloadpodman-f018c07edfb4d83b7c97e98223a4a7a56fd12d8b.tar.gz
podman-f018c07edfb4d83b7c97e98223a4a7a56fd12d8b.tar.bz2
podman-f018c07edfb4d83b7c97e98223a4a7a56fd12d8b.zip
System tests: show one-line config overview
We're running into problems that are impossible to diagnose because we have no idea if the SUT is using netavark or CNI. We've previously run into similar problems with runc/crun, or cgroups 1/2. This adds a one-line 'echo' with important system info. Now, when viewing a full test log, it will be possible to view system settings in one glance. Signed-off-by: Ed Santiago <santiago@redhat.com>
-rw-r--r--test/system/001-basic.bats17
1 files changed, 17 insertions, 0 deletions
diff --git a/test/system/001-basic.bats b/test/system/001-basic.bats
index 9b0a71285..e36142188 100644
--- a/test/system/001-basic.bats
+++ b/test/system/001-basic.bats
@@ -33,6 +33,23 @@ function setup() {
fi
}
+@test "podman info" {
+ # These will be displayed on the test output stream, offering an
+ # at-a-glance overview of important system configuration details
+ local -a want=(
+ 'Arch:{{.Host.Arch}}'
+ 'OS:{{.Host.Distribution.Distribution}}{{.Host.Distribution.Version}}'
+ 'Runtime:{{.Host.OCIRuntime.Name}}'
+ 'Rootless:{{.Host.Security.Rootless}}'
+ 'Events:{{.Host.EventLogger}}'
+ 'Logdriver:{{.Host.LogDriver}}'
+ 'Cgroups:{{.Host.CgroupsVersion}}+{{.Host.CgroupManager}}'
+ 'Net:{{.Host.NetworkBackend}}'
+ )
+ run_podman info --format "$(IFS='/' echo ${want[@]})"
+ echo "# $output" >&3
+}
+
@test "podman --context emits reasonable output" {
# All we care about here is that the command passes