deployment fails if container volume source is a docker/podman volume and not a filesystem path
Bug #1843734 reported by
Alex Schultz
This bug affects 1 person
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
tripleo |
Fix Released
|
High
|
Alex Schultz |
Bug Description
Both docker and podman support using a volume name as part of a volume mount. We added logic into paunch to throw an error if the source didn't exist and we assumed it was always a file system path. Since this can also be container volume, we need to adjust the logic to handle checking for container volumes.
Changed in tripleo: | |
assignee: | nobody → Alex Schultz (alex-schultz) |
To post a comment you must log in.
Related fix proposed to branch: stable/queens /review. opendev. org/681789
Review: https:/