Assert that tempest playbook is not executed with a local connection

[markgoddard]

This playbook copies files to temporary directories. They must be on the
host rather than in the Kayobe container in order to be accessible by the
docker-rally container.

[jovial]

If /tmp was bind mounted into the kayobe container would the local connection plugin work?

[markgoddard]

Possibly, but it's a bit messy

[jovial]

Possibly, but it's a bit messy

The only reason I'm hesitant is because I think we might use it like that at one customer. Could we instead try creating a file with docker and seeing if shows up in our /tmp:

           docker run --rm --entrypoint=/usr/bin/bash
           --name tempest
           --network host
           {{ rally_image_full }} touch /tmp/kayobe-automation-run-tempest.yml

Although that might the customer where @scrungus hit this issue.

[markgoddard]

Possibly, but it's a bit messy

The only reason I'm hesitant is because I think we might use it like that at one customer. Could we instead try creating a file with docker and seeing if shows up in our /tmp:

           docker run --rm --entrypoint=/usr/bin/bash
           --name tempest
           --network host
           {{ rally_image_full }} touch /tmp/kayobe-automation-run-tempest.yml

Although that might the customer where @scrungus hit this issue.

Possibly - my advice was to not use a local connection, and that's why I came up with this change :)