test job filled up root volume on xci32
One theory is that multiple jobs tried to work with the same machine at the same time.
Mitigate this by somehow provision a unique key per machine, e.g.
- provide a unique pubkey via the kickstart and have it appended to /root/.ssh/authorized_keys
- create and add a key to be used by the recipe after the provision is done so provision is done with the default key, but the tests will use the recipe key
Edited by Michael Hofmann