copr: builders: shorter health check timeout for aarch64
When the builder gets removed by resalloc, the new one (with the same IP) gets created pretty quickly now. This could lead to redis database clash (two VMs with the same IP).
This commit is contained in:
parent
8ae074289b
commit
8e9f2ae762
1 changed files with 1 additions and 1 deletions
|
@ -66,7 +66,7 @@ group2_archs=aarch64
|
|||
group2_spawn_playbook=/home/copr/provision/builderpb_libvirt_aarch64.yml
|
||||
group2_terminate_playbook=/home/copr/provision/terminatepb_libvirt_aarch64.yml
|
||||
group2_vm_health_check_period=30
|
||||
group2_vm_health_check_max_time=120
|
||||
group2_vm_health_check_max_time=80
|
||||
|
||||
{% if not devel %}
|
||||
group2_max_vm_per_user=4
|
||||
|
|
Loading…
Add table
Add a link
Reference in a new issue