+1 On Wed, 20 Mar 2019 at 09:40, Pierre-Yves Chibon <pingou@xxxxxxxxxxxx> wrote: > > On Wed, Mar 20, 2019 at 01:32:09PM +0100, Clement Verna wrote: > > After looking at the data it seems that a timeout of about 2 minutes > > would improve the situation without making bodhi's cron job too long. > > > > This is my revised patch > > > > diff --git a/roles/openshift-apps/greenwave/templates/buildconfig.yml > > b/roles/openshift-apps/greenwave/templates/buildconfig.yml > > index d836b482d..3ed86258f 100644 > > --- a/roles/openshift-apps/greenwave/templates/buildconfig.yml > > +++ b/roles/openshift-apps/greenwave/templates/buildconfig.yml > > @@ -30,7 +30,7 @@ spec: > > > > # Become non-root again > > USER 1001 > > - ENTRYPOINT docker/install-ca.sh && gunicorn-3 --workers 8 > > --timeout 660 --graceful-timeout 300 --bind 0.0.0.0:8080 > > --access-logfile=- --enable-stdio-inheritance greenwave.wsgi:app > > + ENTRYPOINT docker/install-ca.sh && gunicorn-3 --workers 8 > > --timeout 127 --bind 0.0.0.0:8080 --access-logfile=- > > --enable-stdio-inheritance greenwave.wsgi:app > > strategy: > > type: Docker > > dockerStrategy: > > -- > > 2.20.1 > > > > +1s ? -1s ? > > +1 for me :) > > Pierre > _______________________________________________ > infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx > To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx > Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html > List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines > List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx -- Stephen J Smoogen. _______________________________________________ infrastructure mailing list -- infrastructure@xxxxxxxxxxxxxxxxxxxxxxx To unsubscribe send an email to infrastructure-leave@xxxxxxxxxxxxxxxxxxxxxxx Fedora Code of Conduct: https://getfedora.org/code-of-conduct.html List Guidelines: https://fedoraproject.org/wiki/Mailing_list_guidelines List Archives: https://lists.fedoraproject.org/archives/list/infrastructure@xxxxxxxxxxxxxxxxxxxxxxx