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

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.

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?

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

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