summaryrefslogtreecommitdiff
path: root/test/e2e/system_df_test.go
diff options
context:
space:
mode:
authorJordan Christiansen <xordspar0@gmail.com>2021-03-26 22:10:43 -0500
committerMatthew Heon <mheon@redhat.com>2021-03-29 11:32:46 -0400
commit3d1aaffdbb2fafae5f27467c59efc7ec7314c154 (patch)
tree641254fa7533e6757bd4cf0261eeddd3bfc0c996 /test/e2e/system_df_test.go
parentd498022fdde96ef1eb028ea89bb68bf01ca495c5 (diff)
downloadpodman-3d1aaffdbb2fafae5f27467c59efc7ec7314c154.tar.gz
podman-3d1aaffdbb2fafae5f27467c59efc7ec7314c154.tar.bz2
podman-3d1aaffdbb2fafae5f27467c59efc7ec7314c154.zip
Add problematic volume name to kube play error messages
When kube play fails to create a volume, it should say which volume had the problem so the user doesn't have to guess. For the following pod spec: apiVersion: v1 kind: Pod metadata: name: mypod spec: containers: - name: myfrontend image: nginx volumeMounts: - mountPath: "/var/www/html" name: mypd volumes: - name: mypd hostPath: path: /var/blah podman will now report: Error: failed to create volume "mypd": error in parsing HostPath in YAML: error checking path "/var/blah": stat /var/blah: no such file or directory Signed-off-by: Jordan Christiansen <xordspar0@gmail.com>
Diffstat (limited to 'test/e2e/system_df_test.go')
0 files changed, 0 insertions, 0 deletions