Adam Williamson 13f59ad0eb openqa/worker: have swtpm service restart on success ... This is because swtpm is designed not to be persistent, it's sort of tied to a single "system" (VM in this case). We can't expect an instance will stick around after it's been "used", it doesn't do that, it exits successfully. So we need to restart it when that happens. Signed-off-by: Adam Williamson <awilliam@redhat.com>		2020-09-08 10:56:12 -07:00
..
createhdds	Add the createhdds cronjob file to worker role	2017-08-17 14:37:37 -07:00
ifcfg-br0	openqa/worker: configure to use 172. IP range not 10.	2020-07-23 17:27:19 -07:00
ifup-pre-local	use an ifup-pre-local for tap device creation	2016-04-27 15:46:13 -07:00
openqa-ppc64-prep.service	openqa/worker: run the ppc64 script hourly	2017-12-21 16:55:35 -08:00
openqa-ppc64-prep.sh	openqa/worker: add boot script to fix KVM perms and disable SMT	2017-09-15 17:52:15 -07:00
openqa-swtpm@.service	openqa/worker: have swtpm service restart on success	2020-09-08 10:56:12 -07:00
os-autoinst-openvswitch.sysconfig	openqa/worker: configure to use 172. IP range not 10.	2020-07-23 17:27:19 -07:00
scratchrepo.repo	openqa: correct scratch repo config filename	2020-04-30 12:38:48 -07:00
systemd-swtpm.pp	openqa/worker: set up swtpm service on tap worker hosts	2020-06-24 16:59:11 -07:00
systemd-swtpm.te	openqa/worker: set up swtpm service on tap worker hosts	2020-06-24 16:59:11 -07:00