Greetings. image composes using oz take a long time on our s390x image builder, (due to them being in another datacenter). They take so long, they timeout. See: https://pagure.io/koji/pull-request/837 from sinny and https://pagure.io/koji/pull-request/841 which makes this value configurable in kojid.conf I would like to: 1. Update koji on buildvm-s390x-02 to the version I just built in rawhide/f28 that has a backport of the patch that makes this value configurable. 2. Apply the following ansible patch to set the timeout only on the buildvm-s390x-02 builder: diff --git a/roles/koji_builder/templates/kojid.conf b/roles/koji_builder/templates/kojid.conf index 832d80c..9f10d9c 100644 --- a/roles/koji_builder/templates/kojid.conf +++ b/roles/koji_builder/templates/kojid.conf @@ -20,7 +20,12 @@ maxjobs=25 keepalive=False rpmbuild_timeout=172800 - +{% if ansible_hostname.startswith('buildvm-s390x-02') %} +; Set oz timeout higher on x390x image builder to allow it to finish. +; Install timeout(seconds) for image build +; if it's unset, use the number in /etc/oz/oz.cfg, supported since oz-0.16.0 +oz_install_timeout=14400 +{% endif %} use_createrepo_c=True {% if host in groups['buildvm-s390x'] %} 3. Run the playbook on it to update the config and restart kojid. +1s? kevin
Attachment:
signature.asc
Description: OpenPGP digital signature
_______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx
