infrastructure June 2019

infrastructure@lists.fedoraproject.org

24 participants
25 discussions

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

06 Jun '19

Dear all, You are kindly invited to the meeting: Fedora Infrastructure on 2019-06-06 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/

3 2

RFC: Deploying coreos-koji-tagger in Fedora Openshift
by Dusty Mabe 05 Jun '19

05 Jun '19

This is a request for comments on deploying the coreos-koji-tagger service in Fedora OpenShift. The details for the request and what the service are in in the RFR ticket [1]. If it's sufficient to have the conversation there, I'd prefer that. https://pagure.io/fedora-infrastructure/issue/7870 Thanks, Dusty

1 0

[PATCH] Add f30-flatpak to the list of tags we sync
by Owen Taylor 04 Jun '19

04 Jun '19

From: "Owen W. Taylor" <otaylor(a)fishsoup.net> We're now building Fedora 30 Flatpaks based on the F30 runtime, so we need to populate the f30-flatpak tag based on the contents of Pagure. --- roles/bodhi2/backend/files/koji-sync-listener.py | 2 +- roles/bodhi2/backend/tasks/main.yml | 2 +- 2 files changed, 2 insertions(+), 2 deletions(-) diff --git a/roles/bodhi2/backend/files/koji-sync-listener.py b/roles/bodhi2/backend/files/koji-sync-listener.py index 5d65cc164..1ea07ad53 100644 --- a/roles/bodhi2/backend/files/koji-sync-listener.py +++ b/roles/bodhi2/backend/files/koji-sync-listener.py @@ -23,7 +23,7 @@ def handle(content): sys.stdout.flush() # XXX If you modify this taglist. Please also modify the other copy in # bodhi2/backend/tasks/main.yml - taglist = 'f31 f31-container f31-modular f30 f30-container f30-modular f29 f29-container f29-flatpak f29-modular epel7 dist-6E-epel module-package-list modular' + taglist = 'f31 f31-container f31-modular f30 f30-container f30-flatpak f30-modular f29 f29-container f29-flatpak f29-modular epel7 dist-6E-epel module-package-list modular' cmd = [ '/usr/local/bin/owner-sync-pagure', '--package', package, diff --git a/roles/bodhi2/backend/tasks/main.yml b/roles/bodhi2/backend/tasks/main.yml index 8867d11da..13014d08e 100644 --- a/roles/bodhi2/backend/tasks/main.yml +++ b/roles/bodhi2/backend/tasks/main.yml @@ -65,7 +65,7 @@ # bodhi2/backend/files/koji-sync-listener.py # This cronjob runs only once a day. The listener script runs reactively. cron: name="owner-sync" minute="15" hour="4" user="root" - job="/usr/local/bin/lock-wrapper owner-sync '/usr/local/bin/owner-sync-pagure f31 f31-container f31-modular f30 f30-container f30-modular f29 f29-container f29-flatpak f29-modular epel7 dist-6E-epel module-package-list modular'" + job="/usr/local/bin/lock-wrapper owner-sync '/usr/local/bin/owner-sync-pagure f31 f31-container f31-modular f30 f30-container f30-flatpak f30-modular f29 f29-container f29-flatpak f29-modular epel7 dist-6E-epel module-package-list modular'" cron_file=update-koji-owner when: env == "production" tags: -- 2.21.0

1 0

Compose Tracker Discussion
by Mohan Boddu 03 Jun '19

03 Jun '19

Hi, As part of https://fedora-infra-docs.readthedocs.io/en/latest/sysadmin-guide/sops/requ…, I am sending this email to get the discussion started on deploying compose tracker [1] on to infra openshift instance. Compose Tracker is designed to track all the failed composes and will create a ticket in https://pagure.io/releng/failed-composes for everyone to look at and collaboratively work on solving the problem. It files the ticket with some debug information and a link to the koji failed task. It has been used which was deployed by Dusty for a while, we are now moving it to make it official. Please let me know if you have any questions. [1] https://pagure.io/releng/compose-tracker Thanks, Mohan Boddu.

1 0

state of koji work
by Kevin Fenzi 02 Jun '19

02 Jun '19

Greetings. Since I am out on PTO all next week, I thought I would share a status of where we are with koji so others could continue the work in my absense. We have a number of things that need updates on koji builders. * mock 1.4.15+ is needed for dynamic buildrequires * createrepo_c 0.14.1-2+ is needed for epel8/fedora non modular builds against modules * koji build with backported patches for: ** seperate srpm repos with buildroot source repos ** bare mode repo merging needed for epel8/fedora buildroot ** dynamic buildrequires (along with newer mock) * oz and imagefactory have gone python3 in f31/rawhide, and oz isn't installable in f30 anymore. So, I have built a koji in rawhide with all the patches we need. I have then built in f29/f30-infra tags all the stuff we need: koji with patches createrepo_c oz imagefactory A sticking point for updating has been that our armv7 builders are stuck on f27 due to a kernel (or perhaps userspace?) bug that causes then to pause when doing kernel/glibc/other builds. pbrobinson and pwhalen are trying to isolate this and fix it, but until then it looks like we can move them to fedora 29 + a specific older kernel. I have setup a kickstart that installs this kernel and set ansible to disallow dnf-automatic updating the kernel on them. I've been testing with buildvm-armv7-22 in prod, and buildvm-armv7-01.stg in staging, and so far they have survived several kernel builds. I have updated all of staging with the above packages. What still needs doing next week: * reinstall all the prod armv7 builders with the f29 kickstart and confirm they don't blow up. * promote createrepo_c, koji, oz, imagefactory builds from f29-infra-stg to f29-infra, and epel7-infra-stg to epel7-infra * update koji hubs and all builders to above packages. * watch for problems with oz/imagefactory/createrepo_c/koji and fix or revert. * profit After I get back we can look at moving to f30, but for now f29 should work. Hopefully by then we will have figured out the armv7 issue and be able to move them to the latest kernel. I might have time later tonight/tomorrow to work further on this, but not sure I will. If so, I'll update this thread. If not, it will have to wait until I get back from vacation, or someone else will need to move it forward next week. Thanks, kevin

1 0

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure June 2019