Re: FBR: Renew TLS certificate for whatcanidoforfedora.org
On 3/13/19 12:53 PM, Kevin Fenzi wrote: > +1 > > kevin I went ahead and ran this as I was running the ansible playbook for nagios anyhow. Thanks! kevin signature.asc Description: OpenPGP digital signature ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@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.fedoraproject.org
Fedora 30 Beta Release Readiness meeting
Dear all, Join us on irc.freenode.net in #fedora-meeting-1 for the Fedora 30 Beta Release Readiness meeting. This meeting will be held on Thursday, 2018-03-21 at 19:00 UTC. We will meet to make sure we are coordinated and ready for the Beta release of Fedora 30. Please note that this meeting will be held even if the release is delayed at the Go/No-Go meeting on the same day two hours earlier. You may receive this message several times in order to open this meeting to the teams and to raise awareness, so hopefully more team representatives will come to this meeting. This meeting works best when we have representatives from all of the teams. For more information, see https://fedoraproject.org/wiki/Release_Readiness_Meetings. View the meeting on Fedocal: https://apps.fedoraproject.org/calendar/Fedora%20release/2019/3/21/#m9492 -- Ben Cotton Fedora Program Manager TZ=America/Indiana/Indianapolis ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@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.fedoraproject.org
Re: FBR - Greenwave investigation bigger timeout
+1 kevin signature.asc Description: OpenPGP digital signature ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@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.fedoraproject.org
Re: FBR - Greenwave investigation bigger timeout
> Last +1 for me of the day. Thanks :-) > > On Fri, 15 Mar 2019 at 15:22, Clement Verna wrote: ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@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.fedoraproject.org
Re: FBR - Greenwave investigation bigger timeout
Last +1 for me of the day. On Fri, 15 Mar 2019 at 15:22, Clement Verna 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-le...@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.fedoraproject.org -- Stephen J Smoogen. ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@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.fedoraproject.org
Re: FBR - Greenwave investigation bigger timeout
> 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-le...@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.fedoraproject.org
Re: FBR - Greenwave investigation bigger timeout
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
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@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.fedoraproject.org
FBR - Greenwave investigation bigger timeout
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:
--
+1s ?
Thanks
___
infrastructure mailing list -- infrastructure@lists.fedoraproject.org
To unsubscribe send an email to infrastructure-le...@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.fedoraproject.org
Re: FBR: Greenwave increase gunicorn worker timeout
+1 On Fri, 15 Mar 2019 at 10:18, Clement Verna wrote: > > Hi all, > > So after setting higher timeout to the openshift route, it seems that > now we are hitting gunicorn worker default timeout (30s). > > The following patch increase this value. > > diff --git a/roles/openshift-apps/greenwave/templates/buildconfig.yml > b/roles/openshift-apps/greenwave/templates/buildconfig.yml > index 7bb5420ba..e293809b8 100644 > --- a/roles/openshift-apps/greenwave/templates/buildconfig.yml > +++ b/roles/openshift-apps/greenwave/templates/buildconfig.yml > @@ -30,6 +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 >strategy: > type: Docker > dockerStrategy: > -- > 2.20.1 > > +1s ? > > Thanks > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to infrastructure-le...@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.fedoraproject.org -- Stephen J Smoogen. ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@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.fedoraproject.org
Re: FBR: Greenwave increase gunicorn worker timeout
On Fri, Mar 15, 2019 at 03:17:37PM +0100, Clement Verna wrote: > Hi all, > > So after setting higher timeout to the openshift route, it seems that > now we are hitting gunicorn worker default timeout (30s). > > The following patch increase this value. > > diff --git a/roles/openshift-apps/greenwave/templates/buildconfig.yml > b/roles/openshift-apps/greenwave/templates/buildconfig.yml > index 7bb5420ba..e293809b8 100644 > --- a/roles/openshift-apps/greenwave/templates/buildconfig.yml > +++ b/roles/openshift-apps/greenwave/templates/buildconfig.yml > @@ -30,6 +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 >strategy: > type: Docker > dockerStrategy: > -- > 2.20.1 +1 for me Pierre ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@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.fedoraproject.org
FBR: Greenwave increase gunicorn worker timeout
Hi all, So after setting higher timeout to the openshift route, it seems that now we are hitting gunicorn worker default timeout (30s). The following patch increase this value. diff --git a/roles/openshift-apps/greenwave/templates/buildconfig.yml b/roles/openshift-apps/greenwave/templates/buildconfig.yml index 7bb5420ba..e293809b8 100644 --- a/roles/openshift-apps/greenwave/templates/buildconfig.yml +++ b/roles/openshift-apps/greenwave/templates/buildconfig.yml @@ -30,6 +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 strategy: type: Docker dockerStrategy: -- 2.20.1 +1s ? Thanks ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@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.fedoraproject.org
Re: FBR: Increase the openshift route timeout for greenwave
On Fri, 15 Mar 2019 at 07:46, Pierre-Yves Chibon wrote: > > On Fri, Mar 15, 2019 at 07:41:35AM -0400, Stephen John Smoogen wrote: > > On Fri, 15 Mar 2019 at 07:40, Stephen John Smoogen wrote: > > > > > > Is there a reason why it takes greenwave 5 minutes to come back with an > > > answer? > > > > > > > Better question. Is there a reason why it takes more than 30 seconds > > for greenwave to come back with an answer? > > For updates containing a large number of builds (the threshold being undefined > at this time), it takes a while to greenwave to retrieve all the test results > from resultsdb. > This is why some requests may take a while. > OK in that case +1 as it is a resource contention outside of what can be fixed quickly. > > Pierre > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to infrastructure-le...@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.fedoraproject.org -- Stephen J Smoogen. ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@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.fedoraproject.org
Re: FBR: Increase the openshift route timeout for greenwave
On Fri, Mar 15, 2019 at 07:41:35AM -0400, Stephen John Smoogen wrote: > On Fri, 15 Mar 2019 at 07:40, Stephen John Smoogen wrote: > > > > Is there a reason why it takes greenwave 5 minutes to come back with an > > answer? > > > > Better question. Is there a reason why it takes more than 30 seconds > for greenwave to come back with an answer? For updates containing a large number of builds (the threshold being undefined at this time), it takes a while to greenwave to retrieve all the test results from resultsdb. This is why some requests may take a while. Pierre ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@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.fedoraproject.org
Re: FBR: Increase the openshift route timeout for greenwave
Is there a reason why it takes greenwave 5 minutes to come back with an answer? On Fri, 15 Mar 2019 at 07:21, Pierre-Yves Chibon wrote: > > On Fri, Mar 15, 2019 at 12:11:45PM +0100, Clement Verna wrote: > > Hi all, > > > > After doing some investigation on bodhi requests to greenwave I found > > that the requests are hitting a default 30 seconds timeout from the > > openshift route > > (https://stackoverflow.com/questions/47812807/openshift-service-proxy-timeout). > > > > I would like to increase this timeout to 330 seconds, greenwave will > > timeout after 300 seconds. > > > > For this the following command needs to be run : > > > > oc project greenwave > > oc annotate route greenwave-web --overwrite > > haproxy.router.openshift.io/timeout=330s > > oc annotate route web-pretty --overwrite > > haproxy.router.openshift.io/timeout=330s > > > > I ll be looking at how we can add this into ansible. > > > > +1s ? > > +1 for me > > > Thanks, > Pierre > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to infrastructure-le...@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.fedoraproject.org -- Stephen J Smoogen. ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@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.fedoraproject.org
Re: FBR: Increase the openshift route timeout for greenwave
On Fri, 15 Mar 2019 at 07:40, Stephen John Smoogen wrote: > > Is there a reason why it takes greenwave 5 minutes to come back with an > answer? > Better question. Is there a reason why it takes more than 30 seconds for greenwave to come back with an answer? > On Fri, 15 Mar 2019 at 07:21, Pierre-Yves Chibon wrote: > > > > On Fri, Mar 15, 2019 at 12:11:45PM +0100, Clement Verna wrote: > > > Hi all, > > > > > > After doing some investigation on bodhi requests to greenwave I found > > > that the requests are hitting a default 30 seconds timeout from the > > > openshift route > > > (https://stackoverflow.com/questions/47812807/openshift-service-proxy-timeout). > > > > > > I would like to increase this timeout to 330 seconds, greenwave will > > > timeout after 300 seconds. > > > > > > For this the following command needs to be run : > > > > > > oc project greenwave > > > oc annotate route greenwave-web --overwrite > > > haproxy.router.openshift.io/timeout=330s > > > oc annotate route web-pretty --overwrite > > > haproxy.router.openshift.io/timeout=330s > > > > > > I ll be looking at how we can add this into ansible. > > > > > > +1s ? > > > > +1 for me > > > > > > Thanks, > > Pierre > > ___ > > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > > To unsubscribe send an email to infrastructure-le...@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.fedoraproject.org > > > > -- > Stephen J Smoogen. -- Stephen J Smoogen. ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@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.fedoraproject.org
Re: FBR: Increase the openshift route timeout for greenwave
On Fri, Mar 15, 2019 at 12:11:45PM +0100, Clement Verna wrote: > Hi all, > > After doing some investigation on bodhi requests to greenwave I found > that the requests are hitting a default 30 seconds timeout from the > openshift route > (https://stackoverflow.com/questions/47812807/openshift-service-proxy-timeout). > > I would like to increase this timeout to 330 seconds, greenwave will > timeout after 300 seconds. > > For this the following command needs to be run : > > oc project greenwave > oc annotate route greenwave-web --overwrite > haproxy.router.openshift.io/timeout=330s > oc annotate route web-pretty --overwrite > haproxy.router.openshift.io/timeout=330s > > I ll be looking at how we can add this into ansible. > > +1s ? +1 for me Thanks, Pierre ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@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.fedoraproject.org
FBR: Increase the openshift route timeout for greenwave
Hi all, After doing some investigation on bodhi requests to greenwave I found that the requests are hitting a default 30 seconds timeout from the openshift route (https://stackoverflow.com/questions/47812807/openshift-service-proxy-timeout). I would like to increase this timeout to 330 seconds, greenwave will timeout after 300 seconds. For this the following command needs to be run : oc project greenwave oc annotate route greenwave-web --overwrite haproxy.router.openshift.io/timeout=330s oc annotate route web-pretty --overwrite haproxy.router.openshift.io/timeout=330s I ll be looking at how we can add this into ansible. +1s ? ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@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.fedoraproject.org
