infrastructure August 2018

infrastructure@lists.fedoraproject.org

25 participants
51 discussions

Flock Videos for Infra - Incomplete
by Zach Villers 30 Aug '18

30 Aug '18

Here is a link to a playlist for a few videos from Flock 2018 that may help apprentices/contributors learn more about Fedora Infrastructure. I don't think _all_ the talks have been posted yet. I will try to update the playlist if I see more. Flock Playlist <cid:part1.783AF692.5A1CDF15@mailup.net>

2 1

Meeting Agenda Item: Introduction Jakub Kadlcik
by Jakub Kadlcik 30 Aug '18

30 Aug '18

Hello guys, I am (kinda) new here and I want to introduce myself. My name is Jakub Kadlcik (fas: frostyx) and I am a Red Hat employee working on Copr. Currently, I am a Fedora Infra apprentice and I would like to be sponsored into sysadmin group in order to be fully capable of maintaining Copr machines. I have already written several patches for Copr playbooks in Fedora Infra ansible repo - mainly regarding MBS deployment and small maintenance tasks, such as builders upgrade. More recently, I worked on https certificates for copr-fe-dev. However, my main focus is development (mainly in python). I still don't feel 100% confident in ansible and sysadmin stuff, so this is where I want to improve most. Also, I really enjoy writing blog posts [1] and documentation, so maybe I could be helpful also in this realm. [1] http://frostyx.cz/posts/ Jakub

1 0

Proposed Meeting Agenda for 2018-08-30
by Stephen John Smoogen 29 Aug '18

29 Aug '18

Here is the current agenda for tomorrow's meeting. Please add items to the gobby document as needed = Preamble = The infrastructure team will be having its weekly meeting tomorrow, 2018-08-30 at 14:00 UTC in #fedora-meeting-1 on the freenode network. We have a gobby document (see: https://fedoraproject.org/wiki/Gobby ) fedora-infrastructure-meeting-next is the document. 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 (2018-08-30) #meetingname infrastructure #topic aloha #chair nirik pingou puiterwijk relrod smooge tflink threebean = 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 = 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 tflink is on extended PTO #info Beta Freeze is in effect. All changes to frozen systems in Infrastructure will require +1 #info bodhi 3.9.0 deployed on Monday = 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 Nirik is on call from 2018-08-30->2018-09-06 #info Relrod is on call from 2018-09-06->2018-09-13 #info ??? is on call from 2018-09-13->2018-09-20 #info Summary of last week: (from Smooge) #topic Tickets discussion #info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket Go thru each ticket one by one = 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

[PATCH] bodhi-pungi: specify ostree ref in config and updates for f29
by Dusty Mabe 29 Aug '18

29 Aug '18

Now that we can specify the ostree_ref in the config we can stop having to choose various fedora-atomic-host-updates-{stable,testing}.json files. For silverblue we are also changing the ref to silverblue away from workstation so we'll only specify ostree_ref if f29+ and let the json files still specify "workstation" for f27 and f28. --- roles/bodhi2/backend/templates/pungi.rpm.conf.j2 | 24 ++++++++++++++++++++---- 1 file changed, 20 insertions(+), 4 deletions(-) diff --git a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 index 4c436dbb1..a523674e1 100644 --- a/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 +++ b/roles/bodhi2/backend/templates/pungi.rpm.conf.j2 @@ -121,7 +121,7 @@ ostree = { "version": "!VERSION_FROM_VERSION_DATE_RESPIN", [% endif %] "force_new_commit": True - "treefile": "fedora-atomic-host-updates-[[ request.name ]].json", + "treefile": "fedora-atomic-host.json", "config_url": "https://pagure.io/fedora-atomic.git", "config_branch": "f[[ release.version ]]", "repo": [ @@ -138,6 +138,11 @@ ostree = { [% endif %] ] "ostree_repo": "/mnt/koji/compose/atomic/repo", + [% if request.name == 'stable' %] + "ostree_ref": "fedora/[[ release.version_int ]]/${basearch}/updates/atomic-host", + [% else %] + "ostree_ref": "fedora/[[ release.version_int ]]/${basearch}/testing/atomic-host", + [% endif %] "tag_ref": False, "arches": ["x86_64", [% if release.version_int >= 27 %] @@ -154,11 +159,13 @@ ostree = { [% if release.version_int >= 28 %] "version": "!VERSION_FROM_VERSION_DATE_RESPIN", [% endif %] - [% if release.version_int >= 28 %] + [% if release.version_int >= 29 %] + "treefile": "fedora-silverblue.json", + [% elif release.version_int == 28 %] "treefile": "fedora-atomic-workstation-updates-[[ request.name ]].json", - [% else %] + [% else %] "treefile": "fedora-ostree-workstation-updates-[[ request.name ]].json", - [% endif %] + [% endif %] "config_url": "https://pagure.io/workstation-ostree-config.git", "config_branch": "f[[ release.version ]]", "repo": [ @@ -175,6 +182,15 @@ ostree = { [% endif %] ] "ostree_repo": "/mnt/koji/compose/atomic/repo", + # For f29+ we are changing the ref to silverblue. For f28/f27 let the files + # still specify the workstation ref. + [% if release.version_int >= 29 %] + [% if request.name == 'stable' %] + "ostree_ref": "fedora/[[ release.version_int ]]/${basearch}/updates/silverblue", + [% else %] + "ostree_ref": "fedora/[[ release.version_int ]]/${basearch}/testing/silverblue", + [% endif %] + [% endif %] "tag_ref": False, "arches": ["x86_64"], "failable": ["x86_64"] -- 2.14.4

4 7

FBR: Manually delete the Fedora 29 compose that is failed in Bodhi's DB
by Randy Barlow 29 Aug '18

29 Aug '18

There is a Fedora 29 Compose in Bodhi's DB that has gotten into a weird state due to being run when the process didn't know about Fedora 29. To fix it, I wish to use pshell on bodhi-backend01 to delete it: $ sudo -u apache pshell /etc/bodhi/production.ini >>> c = m.Compose.query.first() >>> m.Session().delete(c) >>> m.Session().commit() +1's?

4 8

Freeze Break: some more bodhi config for f29
by Kevin Fenzi 29 Aug '18

29 Aug '18

> diff --git a/roles/bodhi2/base/templates/production.ini.j2 b/roles/bodhi2/base/templates/production.ini.j2 > index 37d8608..a44ffab 100644 > --- a/roles/bodhi2/base/templates/production.ini.j2 > +++ b/roles/bodhi2/base/templates/production.ini.j2 > @@ -230,6 +230,8 @@ master_repomd = http://download01.phx2.fedoraproject.org/pub/fedora/linux/update > fedora_master_repomd = http://download01.phx2.fedoraproject.org/pub/fedora/linux/updates/%s/%s/rep… > fedora_28_stable_master_repomd = http://download01.phx2.fedoraproject.org/pub/fedora/linux/updates/%s/Everyt… > fedora_28_testing_master_repomd = http://download01.phx2.fedoraproject.org/pub/fedora/linux/updates/testing/%… > +fedora_29_stable_master_repomd = http://download01.phx2.fedoraproject.org/pub/fedora/linux/updates/%s/Everyt… > +fedora_29_testing_master_repomd = http://download01.phx2.fedoraproject.org/pub/fedora/linux/updates/testing/%… > fedora_epel_master_repomd = http://download01.phx2.fedoraproject.org/pub/epel/%s/%s/repodata/repomd.xml > {% endif %} > > @@ -280,6 +282,8 @@ fedora_stable_alt_master_repomd = http://download01.phx2.fedoraproject.org/pub/f > fedora_testing_alt_master_repomd = http://download01.phx2.fedoraproject.org/pub/fedora-secondary/updates/testi… > fedora_28_stable_alt_master_repomd = http://download01.phx2.fedoraproject.org/pub/fedora-secondary/updates/%s/Ev… > fedora_28_testing_alt_master_repomd = http://download01.phx2.fedoraproject.org/pub/fedora-secondary/updates/testi… > +fedora_29_stable_alt_master_repomd = http://download01.phx2.fedoraproject.org/pub/fedora-secondary/updates/%s/Ev… > +fedora_29_testing_alt_master_repomd = http://download01.phx2.fedoraproject.org/pub/fedora-secondary/updates/testi… > {% elif env == 'staging' %} > fedora_stable_alt_master_repomd = https://kojipkgs.stg.fedoraproject.org/compose/updates/f%s-updates/compose/… > fedora_testing_alt_master_repomd = https://kojipkgs.stg.fedoraproject.org/compose/updates/f%s-updates-testing/… > @@ -303,6 +307,7 @@ base_address = https://bodhi{{env_suffix}}.fedoraproject.org/ > fedora_26_primary_arches = armhfp x86_64 > fedora_27_primary_arches = armhfp x86_64 > fedora_28_primary_arches = aarch64 armhfp x86_64 > +fedora_29_primary_arches = aarch64 armhfp x86_64 > > ## > ## Email setting Also we need to restart fedmsg-hub on bodhi-backend01 for this and other things to take effect. +1s? kevin

4 3

FBR: hotfix - Don't clean old mashes
by Randy Barlow 29 Aug '18

29 Aug '18

This replaces the other FBR I filed today. I would like to manually apply (i.e., hotfix) this patch to bodhi-backend01 as a temporary workaround for #7194[0]: diff --git a/bodhi/server/consumers/masher.py b/bodhi/server/consumers/masher.py index ecf88fd3..43c2ac5f 100644 --- a/bodhi/server/consumers/masher.py +++ b/bodhi/server/consumers/masher.py @@ -432,7 +432,6 @@ class ComposerThread(threading.Thread): # Clean old composes self.save_state(ComposeState.cleaning) - clean_old_mashes.remove_old_composes() self.save_state(ComposeState.success) self.success = True For a longer term fix, I will wrap the above dropped line in an if statement that checks a new setting for whether Bodhi should auto-cleanup old composes, and I will include that patch in Bodhi 3.10.0 (planned for release after the current freeze). [0] https://pagure.io/fedora-infrastructure/issue/7194

4 4

FBR : To fix rawhide sync location
by Mohan Boddu 29 Aug '18

29 Aug '18

Fix for https://pagure.io/releng/issue/7731. This can be a temporary fix or permanent fix depends on which way we choose to proceed. If you think we should go back and revert the changes we made to this script and just sync them as part of nightly.sh, please -1 this. diff --git a/roles/bodhi2/backend/files/new-updates-sync b/roles/bodhi2/backend/files/new-updates-sync index e625f50..660b464 100755 --- a/roles/bodhi2/backend/files/new-updates-sync +++ b/roles/bodhi2/backend/files/new-updates-sync @@ -34,9 +34,9 @@ RELEASES = {'rawhide': {'topic': 'fedora', {'ref': 'fedora/rawhide/x86_64/silverblue', 'dest': ATOMICDEST}], 'to': [{'arches': ['x86_64', 'armhfp', 'aarch64', 'source'], - 'dest': os.path.join(RAWHIDEDEST, 'rawhide', 'Everything')}, + 'dest': os.path.join(RAWHIDEDEST, 'rawhide', 'Everything', 'os')}, {'arches': ['i386', 'ppc64le', 's390x'], - 'dest': os.path.join(RAWHIDEALTDEST, 'rawhide', 'Everything')} + 'dest': os.path.join(RAWHIDEALTDEST, 'rawhide', 'Everything', 'os')} ]}}, }, 'f29': {'topic': 'fedora',

3 4

FBR: workaround for #7194
by Randy Barlow 29 Aug '18

29 Aug '18

Fedora 28 will always fail to compose with Bodhi 3.9.0 because of a recent change that is causing some ostree files to be root owned in /mnt/koji/compose/updates/[0]. I filed a ticket to ask for help in deciding a solution to the problem, but we need an immediate solution because the current compose is marked as failed. For a short term workaround, I would like to hot patch bodhi-backend01 with this: diff --git a/bodhi/server/scripts/clean_old_mashes.py b/bodhi/server/scripts/clean_old_mashes.py index f812c6d9..e69de3e1 100644 --- a/bodhi/server/scripts/clean_old_mashes.py +++ b/bodhi/server/scripts/clean_old_mashes.py @@ -27,7 +27,7 @@ from bodhi.server import config # How many of the newest mash dirs to keep during cleanup -NUM_TO_KEEP = 10 +NUM_TO_KEEP = 5 @click.command() Additionally, I would like to run the above as root on a regular basis (perhaps daily) until we decide on a proper solution to #7194. Basically, the current script deletes the most recent 10. This script is run at the end of the compose and is what is failing. At that point, there are going to be 11. If I change the script to some number less than 10 (5 is arbitrary), I can get ahead of what the composer is going to do and cause it to no-op, which will make it succeed. This is not a long term solution. [0] https://pagure.io/fedora-infrastructure/issue/7194

2 5

FBR: Autosigning for post bodhi activation of F29
by Mohan Boddu 29 Aug '18

29 Aug '18

--- a/roles/robosignatory/files/robosignatory.production.py +++ b/roles/robosignatory/files/robosignatory.production.py @@ -132,28 +132,21 @@ config = { "keyid": "cfc659b9", "type": "modular" }, - { - "from": "f29-pending", - "to": "f29", - "key": "fedora-29", - "keyid": "429476b4" - }, + + # Gated bodhi updates { "from": "f29-modular-signing-pending", - "to": "f29-modular", + "to": "f29-modular-updates-testing-pending", "key": "fedora-29", "keyid": "429476b4", "type": "modular" }, { - "from": "f29-modular-updates-candidate", - "to": "f29-modular", + "from": "f29-signing-pending", + "to": "f29-updates-testing-pending", "key": "fedora-29", - "keyid": "429476b4", - "type": "modular" + "keyid": "429476b4" }, - - # Gated bodhi updates { "from": "f28-modular-signing-pending", "to": "f28-modular-updates-testing-pending",

3 2

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

infrastructure August 2018