Hi all
Still going on with greenwave investigation, I would like to double the timeout (from 330s to 660s) to see if that helps getting the last few tests results that are still failing.
I would like to apply the following patch
diff --git a/playbooks/openshift-apps/greenwave.yml b/playbooks/openshift-apps/greenwave.yml index d15499c19..21ce08aeb 100644 --- a/playbooks/openshift-apps/greenwave.yml +++ b/playbooks/openshift-apps/greenwave.yml @@ -95,7 +95,7 @@
tasks: - name: Set the timeout to the openshift route - command: "oc -n greenwave annotate route {{ item }} --overwrite haproxy.router.openshift.io/timeout=330s" + command: "oc -n greenwave annotate route {{ item }} --overwrite haproxy.router.openshift.io/timeout=660s" with_items: - greenwave-web - web-pretty diff --git a/roles/openshift-apps/greenwave/templates/buildconfig.yml b/roles/openshift-apps/greenwave/templates/buildconfig.yml index e293809b8..d836b482d 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 330 --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 660 --graceful-timeout 300 --bind 0.0.0.0:8080 --access-logfile=- --enable-stdio-inheritance greenwave.wsgi:app strategy: type: Docker dockerStrategy:
On Fri, Mar 15, 2019 at 08:10:10PM +0100, Clement Verna wrote:
Hi all
Still going on with greenwave investigation, I would like to double the timeout (from 330s to 660s) to see if that helps getting the last few tests results that are still failing.
I would like to apply the following patch
diff --git a/playbooks/openshift-apps/greenwave.yml b/playbooks/openshift-apps/greenwave.yml index d15499c19..21ce08aeb 100644 --- a/playbooks/openshift-apps/greenwave.yml +++ b/playbooks/openshift-apps/greenwave.yml @@ -95,7 +95,7 @@
tasks: - name: Set the timeout to the openshift route
command: "oc -n greenwave annotate route {{ item }} --overwrite
haproxy.router.openshift.io/timeout=330s"
command: "oc -n greenwave annotate route {{ item }} --overwrite
haproxy.router.openshift.io/timeout=660s" with_items: - greenwave-web - web-pretty diff --git a/roles/openshift-apps/greenwave/templates/buildconfig.yml b/roles/openshift-apps/greenwave/templates/buildconfig.yml index e293809b8..d836b482d 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 330 --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 660 --graceful-timeout 300 --bind 0.0.0.0:8080 --access-logfile=- --enable-stdio-inheritance greenwave.wsgi:app strategy: type: Docker dockerStrategy: --
+1 for me, but please consider making the openshift time out > than the gunicorn one as otherwise they do not appear in the logs of the application. So something like 660 for gunicorn and 750 for openshift would be better I think.
Pierre
On Fri, Mar 15, 2019 at 08:10:10PM +0100, Clement Verna wrote:
+1 for me, but please consider making the openshift time out > than the gunicorn one as otherwise they do not appear in the logs of the application. So something like 660 for gunicorn and 750 for openshift would be better I think.
Sure, that works for me
Pierre
Last +1 for me of the day.
On Fri, 15 Mar 2019 at 15:22, Clement Verna cverna@fedoraproject.org wrote:
On Fri, Mar 15, 2019 at 08:10:10PM +0100, Clement Verna wrote:
+1 for me, but please consider making the openshift time out > than the gunicorn one as otherwise they do not appear in the logs of the application. So something like 660 for gunicorn and 750 for openshift would be better I think.
Sure, that works for me
Pierre
infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-leave@lists.fedoraproject.org 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@lists.fedorapro...
infrastructure@lists.fedoraproject.org