March 2019 - infrastructure - Fedora mailing-lists

[FBR] proxies: adding rewritecond to reverseproxy for ws if remotepath exists
by Tim Flink 25 Mar '19

25 Mar '19

I was hitting an issue where there were multiple reverseproxy instances configured for a single host and some of the rewrite rules were changing the request when they shouldn't be. This patch adds a rewritecond to the websocket rewrite rule to make sure that the REQUEST_URI starts with $remotepath before it's rewritten. --- roles/httpd/reverseproxy/templates/reversepassproxy.conf | 3 +++ 1 file changed, 3 insertions(+) diff --git a/roles/httpd/reverseproxy/templates/reversepassproxy.conf b/roles/httpd/reverseproxy/templates/reversepassproxy.conf index 38950e4..1e4afe0 100644 --- a/roles/httpd/reverseproxy/templates/reversepassproxy.conf +++ b/roles/httpd/reverseproxy/templates/reversepassproxy.conf @@ -47,6 +47,9 @@ SSLProxyEngine On RewriteEngine on RewriteCond %{HTTP:Upgrade} ^WebSocket$ [NC] RewriteCond %{HTTP:Connection} Upgrade [NC] +{% if remotepath is defined %} +RewriteCond %{REQUEST_URI} ^{{ remotepath }}/(.)* +{% endif %} RewriteRule .* "balancer://{{ balancer_name }}-websocket%{REQUEST_URI}" [P] <Proxy "balancer://{{balancer_name}}"> -- 1.8.3.1

3 3

FYI FBR: libseccomp upgraded on builders
by Kevin Fenzi 25 Mar '19

25 Mar '19

I am treating this one as an outage so I already applied it, but FYI: * last night our fedora29 builders applied a qemu security update. * after this update, images fail to build with: "internal error: process exited while connectin g to monitor: 2019-03-25T15:46:33.471016Z qemu-system-x86_64: -sandbox on,obsolete=deny,elevateprivileges=deny,spawn=deny ,resourcecontrol=deny: failed to install seccomp syscall filter in the kernel" * The 'fix' is to update also libseccomp (which has been in stable updates for 10 days, but we didn't apply it because it was not a security update and we are in freeze). Since this was preventing any compose, I went ahead and applied it to all builders. kevin

1 0

What are we going to do about sigul?
by Neal Gompa 25 Mar '19

25 Mar '19

Hey all, So, we've got a bit of a problem. The sigul package is not installable in Fedora 29, and pygpgme is half-broken in Fedora 28 and was retired during Fedora 29 development due to constant breakage. This means that sigul is in danger of being retired in Fedora. Unfortunately, sigul is the only supported signer system for Koji at the moment. What do we want to do here? It's well-known that sigul does not work with GnuPG 2, though I vaguely recall that some work was done to try to fix this. Do we want to port sigul to python3-gpg, switching Sigul to Python 3 and the official gpgme bindings so that it works with GnuPG 2? Or do we want to adapt the bridge to work with obs-signd (which is already used by Copr)? -- 真実はいつも一つ！/ Always, there's only one truth!

4 6

FBR: batcave allows / run bastion playbook for vpn
by Stephen John Smoogen 25 Mar '19

25 Mar '19

I added repospanner to vpn earlier but have not run playbook on bastions [smooge@batcave01 ansible (master)]$ git diff f7c0985d56228bae8332aa3360a086f033e641d8 diff --git a/roles/batcave/files/allows b/roles/batcave/files/allows index 5439b2a..2a721d8 100644 --- a/roles/batcave/files/allows +++ b/roles/batcave/files/allows @@ -107,7 +107,13 @@ require ip 8.43.85.69 require ip 8.43.85.70 require ip 8.43.85.71 require ip 8.43.85.72 +require ip 8.43.85.73 require ip 8.43.85.74 +require ip 8.43.85.75 +require ip 8.43.85.76 +require ip 8.43.85.77 +require ip 8.43.85.78 +require ip 8.43.85.79 # === -- Stephen J Smoogen.

3 3

Re: FBR: update prod tag name in WaiverDB
by Clement Verna 25 Mar '19

25 Mar '19

On Mon, 25 Mar 2019 at 10:49, Yuxiang Zhu <yuxzhu(a)redhat.com> wrote: > > Currently the prod-fedora tag points to the same image as prod tag. > > I just checked `quay.io/factory2/waiverdb:prod-fedora` (sha256:726a6c6465e066bc1056c17b71c16117150266490fed8fa2b096e7bb249eba8e) from quay.io's Web UI. It is built from https://pagure.io/waiverdb/tree/d4ea9bffd9da52efbef147b0e2d42cc726c1d7c6 so the change of messaging is not included. Great Thanks :) It would be +1 for me, but my vote does not count :) > > On Mon, Mar 25, 2019 at 5:39 PM Clement Verna <cverna(a)fedoraproject.org> wrote: >> >> On Mon, 25 Mar 2019 at 10:22, Giulia Naponiello <gnaponie(a)redhat.com> wrote: >> > >> > Hello, >> > we would like to change the name of the tag in quay.io for WaiverDB. Could you make this change? >> >> Does that contains the change to use fedora-messaging instead of fedmsg ? >> >> > >> > Here's the patch: >> > diff --git a/roles/openshift-apps/waiverdb/templates/imagestream.yml b/roles/openshift-apps/waiverdb/templates/imagestream.yml >> > index 3fe37a481..7758ea5c6 100644 >> > --- a/roles/openshift-apps/waiverdb/templates/imagestream.yml >> > +++ b/roles/openshift-apps/waiverdb/templates/imagestream.yml >> > @@ -20,5 +20,5 @@ spec: >> > name: quay.io/factory2/waiverdb:latest >> > {% else %} >> > # This is 'prod' tag is maintained by hand. >> > - name: quay.io/factory2/waiverdb:prod >> > + name: quay.io/factory2/waiverdb:prod-fedora >> > {% endif %} >> > >> > >> > Thank you! >> > Cheers >> > >> > Giulia >> > _______________________________________________ >> > infrastructure mailing list -- infrastructure(a)lists.fedoraproject.org >> > To unsubscribe send an email to infrastructure-leave(a)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.fedorapr… > > > > -- > Thanks, > Yuxiang

2 1

FBR: update prod tag name in WaiverDB
by Giulia Naponiello 25 Mar '19

25 Mar '19

Hello, we would like to change the name of the tag in quay.io for WaiverDB. Could you make this change? Here's the patch: diff --git a/roles/openshift-apps/waiverdb/templates/imagestream.yml b/roles/openshift-apps/waiverdb/templates/imagestream.yml index 3fe37a481..7758ea5c6 100644 --- a/roles/openshift-apps/waiverdb/templates/imagestream.yml +++ b/roles/openshift-apps/waiverdb/templates/imagestream.yml @@ -20,5 +20,5 @@ spec: name: quay.io/factory2/waiverdb:latest {% else %} # This is 'prod' tag is maintained by hand. - name: quay.io/factory2/waiverdb:prod + name: quay.io/factory2/waiverdb:prod-fedora {% endif %} Thank you! Cheers Giulia

2 1

mirrorlist server with Python3
by Adrian Reber 22 Mar '19

22 Mar '19

The latest release of MirrorManager2 is still in updates-testing. I did not want to push this version to updates-released because this is the first Python3 based released. Could someone test the version from updates-testing? Update the mirrorlist container and test it on one of the proxies? Adrian

1 1

FBR: Adding remotepath to websocket balancers
by Tim Flink 22 Mar '19

22 Mar '19

The current template assumes that websockets are at the base of a URL but that is not true for our buildmaster. This patch adds remotepath to the end of the websocket url if remotepath is defined. --- roles/httpd/reverseproxy/templates/reversepassproxy.conf | 8 ++++++++ 1 file changed, 8 insertions(+) diff --git a/roles/httpd/reverseproxy/templates/reversepassproxy.conf b/roles/httpd/reverseproxy/templates/reversepassproxy.conf index deec40b..6131b5d 100644 --- a/roles/httpd/reverseproxy/templates/reversepassproxy.conf +++ b/roles/httpd/reverseproxy/templates/reversepassproxy.conf @@ -29,10 +29,18 @@ SSLProxyEngine On <Proxy "balancer://{{balancer_name}}-websocket"> {% for member in balancer_members %} {% if http_not_https_yes_this_is_insecure_and_i_feel_bad %} + {% if remotepath is defined %} + BalancerMember "ws://{{ member }}{{ remotepath }} + {% else %} BalancerMember "ws://{{ member }}" + {% endif %} + {% else %} + {% if remotepath is defined %} + BalancerMember "ws://{{ member }}{{ remotepath }} {% else %} BalancerMember "wss://{{ member }}" {% endif %} + {% endif %} {% endfor %} </Proxy>

3 3

[Fedocal] Reminder meeting : Bodhi stakeholders' meeting
by bowlofeggs＠fedoraproject.org 21 Mar '19

21 Mar '19

Dear all, You are kindly invited to the meeting: Bodhi stakeholders' meeting on 2019-03-22 from 11:00:00 to 11:45:00 US/Eastern At fedora-meeting-2(a)irc.freenode.net The meeting will be about: We will meet in #fedora-meeting-2 on Freenode to talk about what has been going on in Bodhi development and what is currently planned for the future. There will be an open floor at the end for the airing of grievances, but only after someone pins me before the Festivus tree. The agenda will be posted in the bodhi-stakeholders document in the Infrastructure gobby repository by March 20. Source: https://apps.fedoraproject.org/calendar/meeting/9485/

1 0

FBR for Alessandro Lorenzi for nagios certgetter change.
by Stephen John Smoogen 21 Mar '19

21 Mar '19

I have reviewed this and will sponsor it. ---------- Forwarded message --------- From: Alessandro Lorenzi <pagure(a)pagure.io> Date: Sat, 16 Mar 2019 at 17:24 Subject: [fedora-infrastructure] Issue #7635: Add monitoring for httpd on certgetter To: <smooge(a)gmail.com> neron added a new comment to an issue you are following: `` Hi, first patch in fedora-infrastructure! ``` From 191cd95874e5f2f0141032cc211f2b405255df6d Mon Sep 17 00:00:00 2001 From: Alessandro Lorenzi <alorenzi(a)alorenzi.eu> Date: Sat, 16 Mar 2019 22:10:12 +0100 Subject: [PATCH] Monitoring: add service certgetter http Refs: #7635 --- roles/nagios_server/files/nagios/services/certgetter.cfg | 6 ++++++ 1 file changed, 6 insertions(+) create mode 100644 roles/nagios_server/files/nagios/services/certgetter.cfg diff --git a/roles/nagios_server/files/nagios/services/certgetter.cfg b/roles/nagios_server/files/nagios/services/certgetter.cfg new file mode 100644 index 000000000..2b143ed23 --- /dev/null +++ b/roles/nagios_server/files/nagios/services/certgetter.cfg @@ -0,0 +1,6 @@ +define service { + host_name certgetter01.phx2.fedoraproject.org + service_description certgetter-http + check_command check_http!certgetter01.phx2.fedoraproject.org + use defaulttemplate +} -- 2.17.1 ``` `` To reply, visit the link below or just reply to this email https://pagure.io/fedora-infrastructure/issue/7635 -- Stephen J Smoogen.

5 8

RFR: Message-Tagging-Service
by Chenxiong Qi 20 Mar '19

20 Mar '19

Hi all, This mail is for a new micro-service called Message-Tagging-Service (aka MTS). It serves to tag module build triggered by specific MBS event. More detailed information is provided inside RFR ticket[1]. MTS works with a series of predefined rules to see if a module build should be tagged with one or more tags. There is requirement coming from module maintainers to ensure a module build is tagged into correct platforms to fulfill the dependencies of module metadata. Comment[2] has a specific use case for that. So far, MTS has been containerized and deployed in internal. The image is available from quay.io[3]. We would love to run MTS in Fedora as well in order to make it easier to manage module build tag for module maintainers and rel-eng. If anything is missed for this mail thread, please point out. Questions welcome! Thanks for your time. [1] https://pagure.io/fedora-infrastructure/issue/7563 [2] https://pagure.io/fedora-infrastructure/issue/7563#comment-553774 [3] https://quay.io/repository/factory2/message-tagging-service -- Regards, Chenxiong Qi

3 7

[FBR ] update-fullfiletimelist: make new-updates-sync use the fedora-secondary lock file
by kevin＠scrye.com 20 Mar '19

20 Mar '19

From: Kevin Fenzi <kevin(a)scrye.com> Currently update-fullfiletimelist is called from 4 machines: * rawhide-composer: after rawhide compose * branched-composer: after branched compose * secondary01: in a cron every hour updating only /pub/alt as it can change anytime. * bodhi-backend01: after ever updates sync that has content synced We need bodhi-backend01 to use the same lock as rawhide/branched composers since they update the same modules and we don't want them to step on each other. Signed-off-by: Kevin Fenzi <kevin(a)scrye.com> --- roles/bodhi2/backend/files/new-updates-sync | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/roles/bodhi2/backend/files/new-updates-sync b/roles/bodhi2/backend/files/new-updates-sync index 0fa893b..7d6e456 100755 --- a/roles/bodhi2/backend/files/new-updates-sync +++ b/roles/bodhi2/backend/files/new-updates-sync @@ -234,7 +234,7 @@ def update_fullfilelist(modules): logger.info('No filelists to update') return cmd = ['/usr/local/bin/update-fullfiletimelist', '-l', - '/tmp/update-fullfiletimelist.lock', '-t', '/pub'] + '/pub/fedora-secondary/update-fullfiletimelist.lock', '-t', '/pub'] cmd.extend(modules) run_command(cmd) -- 1.8.3.1

3 2

Meeting Agenda 2019-03-21
by Stephen John Smoogen 20 Mar '19

20 Mar '19

= Preamble = The infrastructure team will be having its weekly meeting tomorrow, 2019-03-21 at 15:00 UTC in #fedora-meeting-1 on the freenode network. We have a gobby document at https://infinote.fedoraproject.org/cgit/infinote/tree/fedora-infrastructure… which can be edited for the agenda (see: https://fedoraproject.org/wiki/Gobby ) Please try and review and edit that document before the meeting and we will use it to have our agenda of things to discuss. A copy as of today is included in this email. If you have something to discuss, add the topic to the discussion area with your name. If you would like to teach other folks about some application or setup in our infrastructure, please add that topic and your name to the learn about section. = Introduction = We will use it over the week before the meeting to gather status and info and discussion items and so forth, then use it in the irc meeting to transfer information to the meetbot logs. = Meeting start stuff = #startmeeting Infrastructure (2019-03-21) #meetingname infrastructure #topic aloha #chair nirik pingou puiterwijk relrod smooge tflink threebean cverna mizdebsk mkonecny = Let new people say hello = #topic New folks introductions #info This is a place where people who are interested in Fedora Infrastructure can introduce themselves #info Getting Started Guide: https://fedoraproject.org/wiki/Infrastructure/GettingStarted = Status / Information / Trivia / Announcements = (We put things here we want others on the team to know, but don't need to discuss) (Please use #info <the thing> - your name) #topic announcements and information #info Beta Freeze Is Currently Going On. Please get FBR for frozen systems. = Things we should discuss = We use this section to bring up discussion topics. Things we want to talk about as a group and come up with some consensus /suor decision or just brainstorm a problem or issue. If there are none of these we skip this section. (Use #topic your discussion topic - your username) #topic Oncall #info bowlofeggs is on call from 2019-03-14 -> 2019-03-21 #info nirik is on call from 2019-03-21 -> 2019-03-28 #info relrod is on call from 2019-03-28 -> 2019-04-04 #info smooge is on call from 2019-04-04 -> 2019-04-11 #info ????? is on call from 2019-04-11 -> 2019-04-18 #info Summary of last week: (from bowlofeggs ) #topic Monitoring discussion #info https://nagios.fedoraproject.org/nagios #info Go over existing out items and fix #topic Tickets discussion #info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket Go thru each ticket one by one #topic Priorities for next week? #info please put tickets needing to be focused on here ===== Put all topics for discussion under here ===== = Apprentice office hours = #topic Apprentice Open office minutes #info A time where apprentices may ask for help or look at problems. Here we will discuss any apprentice questions, try and match up people looking for things to do with things to do, progress, testing anything like that. = Learn about some application or setup in infrastructure = (This section, each week we get 1 person to talk about an application or setup that we have. Just going over what it is, how to contribute, ideas for improvement, etc. Whoever would like to do this, just add the i/nfo in this section. In the event we don't find someone to teach about something, we skip this section and just move on to open floor.) #info = Meeting end stuff = #topic Open Floor #endmeeting -- Stephen J Smoogen.

1 0

Meeting Agenda Item: Introduction Alessandro Lorenzi (aka neron, alorenzi)
by Alessandro Lorenzi 20 Mar '19

20 Mar '19

Hi guys, I've lurked in mailing list and irc enough, It's time to introduce myself! I'm Alessandro Lorenzi, "neron" in fas, "alorenzi" in irc, italian, and fedora user for roughly 1/3 of my life. I was an active Fedora Ambassador in the past. In last few years my free software user group has been disgregated arround the Europe and now is more difficult to organize events. Because of that, my activity in the linux events has been decreased (shame on me). I work as system engineer, my team mainly use puppet, and sometime ansible. Some weeks ago, I don't remember what I was looking for, I've found the fedora-infra-docs and it was an interesting reading, after that I've started to study the fedora-infra git repo and here I am! Bye! -- Alessandro Lorenzi

1 0

FBR : Greenwave gunicorn timeout back to 30s
by Clement Verna 20 Mar '19

20 Mar '19

Hi all, I would like to revert greenwave's gunicorn timeout to the default 30s. Changing it to 10+min was useful for our investigation but it now slows down bodhi cron job. Also the greenwave team is working on fix for this so long term we should not need to have a specific timeout. I am leaving in place the longer OpenShift timeout on the route, so that it is easier to know where the timeout comes from. diff --git a/roles/openshift-apps/greenwave/templates/buildconfig.yml b/roles/openshift-apps/greenwave/templates/buildconfig.yml index d836b482d..7bb5420ba 100644 --- a/roles/openshift-apps/greenwave/templates/buildconfig.yml +++ b/roles/openshift-apps/greenwave/templates/buildconfig.yml @@ -30,7 +30,6 @@ 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 strategy: type: Docker dockerStrategy: -- 2.20.1 +1s ?

4 11

"FBR: To update python3-productmd on compose-x86-01.phx2.fp.o"
by Mohan Boddu 20 Mar '19

20 Mar '19

The recent RC compose failed due to: ValueError: Image: Field 'type' has invalid value: vmdk Support for vmdk was added in python3-productmd-1.21-1.fc29 version. Once updated, this issue should be fixed. Thanks.

3 4

FBR: Add nfs-server/remove ipv6-test
by Stephen John Smoogen 20 Mar '19

20 Mar '19

This will bring 45drives box ready for testing and will remove ipv6-test from ansible. I will need to run the noc.yml after this to remove ipv6-test from nagios. -- Stephen J Smoogen.

3 2

[Fedocal] Reminder meeting : Fedora Infrastructure
by smooge＠gmail.com 20 Mar '19

20 Mar '19

Dear all, You are kindly invited to the meeting: Fedora Infrastructure on 2019-03-21 from 15:00:00 to 16:00:00 UTC At fedora-meeting-1(a)irc.freenode.net The meeting will be about: Weekly Fedora Infrastructure meeting. See infrastructure list for agenda a day before or view it at https://infinote.fedoraproject.org/cgit/infinote/tree/fedora-infrastructure… Source: https://apps.fedoraproject.org/calendar/meeting/22/

1 0

Fedora 30 Beta Release Readiness meeting
by Ben Cotton 20 Mar '19

20 Mar '19

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

1 1

Request for comments: mediawiki-FedoraBadges direct db query
by Rick Elrod 20 Mar '19

20 Mar '19

Hi all, Tahrir is slow, and the endpoint that mediawiki-FedoraBadges uses to get its badge count and badge assertion data from takes about 35 seconds per request. As a result, if a user enables both badge count and badge images on a user page, the two requests combined take well over a minute. This results in mediawiki often bombing the request and rendering an ugly error in place of badges. We get tickets/support requests on this occasionally as well: - https://pagure.io/fedora-infrastructure/issue/7650 Some quick testing shows that the queries I care about for the mediawiki-FedoraBadges plugin take about 70ms to run (in prod). Incurring a 35 second penalty for that seems *crazy* to me. As an alternative, I'd like to propose making a tahrir-readonly user, and modifying the mediawiki-FedoraBadges plugin to query the badges database directly. I played around and got it working in staging, the process was something like: - Create tahrir-readonly postgres user - Grant it readonly perms on the tahrir tables, and connect and usage perms. - Modify the mw plugin - Install php-pgsql on wiki01.stg so it can actually connect After that it seems to work fine. I triggered a cache purge of all wiki pages on stg as well (but on prod, I'd probably just let the cache naturally expire). Pages with badges load almost instantly now (granted the stg data is way less than prod, but still). I'm looking for comments because I don't know if there's anything security-wise I'm overlooking in doing this. At a quick glance, it seems fine -- the new pg user is readonly and very few people have access to LocalSettings.php where the connect info would be stored. But I might well be missing something and want to be safe. Thoughts? Rick

4 5

FBR: Greenwave increase gunicorn worker timeout
by Clement Verna 20 Mar '19

20 Mar '19

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

4 4

[FBR ] releng-compose: Just have compose-x86-01 get the default group values for mem and cpus
by kevin＠scrye.com 19 Mar '19

19 Mar '19

From: Kevin Fenzi <kevin(a)scrye.com> In recent months/years, pungi has started to use more and more memory when gathering package sets. So, give it enough memory to avoid the OOM killer killing composes. Signed-off-by: Kevin Fenzi <kevin(a)scrye.com> --- inventory/host_vars/compose-x86-01.phx2.fedoraproject.org | 2 -- 1 file changed, 2 deletions(-) diff --git a/inventory/host_vars/compose-x86-01.phx2.fedoraproject.org b/inventory/host_vars/compose-x86-01.phx2.fedoraproject.org index 3fa776c..181e3ee 100644 --- a/inventory/host_vars/compose-x86-01.phx2.fedoraproject.org +++ b/inventory/host_vars/compose-x86-01.phx2.fedoraproject.org @@ -12,8 +12,6 @@ ks_repo: http://10.5.126.23/pub/fedora/linux/releases/28/Server/x86_64/os/ virt_install_command: "{{ virt_install_command_two_nic }}" lvm_size: 30000 -mem_size: 16384 -num_cpus: 8 volgroup: /dev/vg_guests eth0_ip: 10.5.125.41 -- 1.8.3.1

3 2

FBR: Increase the openshift route timeout for greenwave
by Clement Verna 19 Mar '19

19 Mar '19

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 ?

4 6

FBR: make iot.fp.o live
by Rick Elrod 19 Mar '19

19 Mar '19

This has been in stg for a while, and I have been asked to make it live. This FBR is for permission to commit this and run the proxy playbook on all proxies. Rick commit fe044fc717517d01211e1995ff9778b7b7906fe4 Author: Rick Elrod <relrod(a)redhat.com> Date: Tue Mar 19 16:59:54 2019 +0000 [fedora-web/iot] make it live Signed-off-by: Rick Elrod <relrod(a)redhat.com> diff --git a/playbooks/include/proxies-fedora-web.yml b/playbooks/include/proxies-fedora-web.yml index 526ba27..7532950 100644 --- a/playbooks/include/proxies-fedora-web.yml +++ b/playbooks/include/proxies-fedora-web.yml @@ -42,7 +42,6 @@ website: arm.fedoraproject.org - role: fedora-web/iot website: iot.fedoraproject.org - when: env == "staging" - role: fedora-web/registry website: registry.fedoraproject.org - role: fedora-web/ostree diff --git a/playbooks/include/proxies-websites.yml b/playbooks/include/proxies-websites.yml index df22e22..352fdde 100644 --- a/playbooks/include/proxies-websites.yml +++ b/playbooks/include/proxies-websites.yml @@ -226,7 +226,6 @@ - iot.stg.fedoraproject.org sslonly: true cert_name: "{{wildcard_cert_name}}" - when: env == "staging" - role: httpd/website site_name: budget.fedoraproject.org diff --git a/roles/fedora-web/build/files/syncStatic.sh b/roles/fedora-web/build/files/syncStatic.sh index 8c5d622..7a541a9 100644 --- a/roles/fedora-web/build/files/syncStatic.sh +++ b/roles/fedora-web/build/files/syncStatic.sh @@ -71,3 +71,4 @@ build fedoracommunity.org build fudcon.fedoraproject.org build start.fedoraproject.org build fedoraproject.org +build iot.fedoraproject.org

3 2

work_mem check for nagios client
by Michal Novotny 19 Mar '19

19 Mar '19

Hello, I've noticed there is no work_mem check https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/nagios… that would test that working memory is inside allowed limits. I've recently made the work_mem check but specific just to COPR: https://clime.cz/0001-copr-fe-working-memory-monitoring.patch. It raises a warning when working memory usage is higher than 80% and criticial if it is higher than 90%. Would it be worth to place this check alongside others in https://infrastructure.fedoraproject.org/cgit/ansible.git/tree/roles/nagios… so that it can be used for any host? Thank you clime

1 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure March 2019