Proposed Meeting Agenda for 2018-08-30

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:

Re: [PATCH] bodhi-pungi: specify ostree ref in config and updates for f29

pushed On 08/29/2018 03:44 PM, Mohan Boddu wrote: > bodhi has pungi-4.1.26-2 , so I guess it should be good. > > +1 > > On Wed, Aug 29, 2018 at 3:42 PM Dusty Mabe > wrote: > > > > On 08/29/2018 03:36 PM, Kevin Fenzi wrote: > > Does this require a specific

Re: FBR: Manually delete the Fedora 29 compose that is failed in Bodhi's DB

This change has been made. 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

Re: FBR: Manually delete the Fedora 29 compose that is failed in Bodhi's DB

On 08/29/2018 03:44 PM, Stephen John Smoogen wrote: > The original is fine. Thank you for the training. I just wanted to make > sure there weren't more objects in the DB, that the query wouldn't give > you a random return from a hashtable etc. > > +1  Excellent. I will make it so. -- Number

Re: FBR: Manually delete the Fedora 29 compose that is failed in Bodhi's DB

On 08/29/2018 03:26 PM, Stephen John Smoogen wrote: > Can you give me more information on what this will due, what could go > wrong and how to recover? If not I don't think I can give an answer. I have two +1's now, but I wanted to make sure you are satisfied too before I take action. Shall I

Re: FBR: Manually delete the Fedora 29 compose that is failed in Bodhi's DB

On Wed, 29 Aug 2018 at 15:37, Randy Barlow wrote: > On 08/29/2018 03:26 PM, Stephen John Smoogen wrote: > > Can you give me more information on what this will due, what could go > > wrong and how to recover? If not I don't think I can give an answer. > > Bodhi has a database model called a

Re: FBR: Manually delete the Fedora 29 compose that is failed in Bodhi's DB

Based on Randy's explanation +1 On Wed, Aug 29, 2018 at 3:37 PM Randy Barlow wrote: > On 08/29/2018 03:26 PM, Stephen John Smoogen wrote: > > Can you give me more information on what this will due, what could go > > wrong and how to recover? If not I don't think I can give an answer. > > Bodhi

Re: [PATCH] bodhi-pungi: specify ostree ref in config and updates for f29

On 08/29/2018 12:41 PM, Dusty Mabe wrote: > > > On 08/29/2018 03:36 PM, Kevin Fenzi wrote: >> Does this require a specific version of pungi? > > Let's see. It looks like there were two related issues that got fixed: > > - https://pagure.io/pungi/issue/777 fixed in 4.1.21 > -

Re: Freeze Break: some more bodhi config for f29

LGTM +1 On Wed, Aug 29, 2018 at 3:24 PM Stephen John Smoogen wrote: > > +1 after review > > On Wed, 29 Aug 2018 at 14:07, Kevin Fenzi wrote: > >> > diff --git a/roles/bodhi2/base/templates/production.ini.j2 >> b/roles/bodhi2/base/templates/production.ini.j2 >> > index 37d8608..a44ffab 100644

Re: [PATCH] bodhi-pungi: specify ostree ref in config and updates for f29

On 08/29/2018 03:36 PM, Kevin Fenzi wrote: > Does this require a specific version of pungi? Let's see. It looks like there were two related issues that got fixed: - https://pagure.io/pungi/issue/777 fixed in 4.1.21 - https://pagure.io/pungi/issue/866 fixed in 4.1.23 so do we have 4.1.23+

Re: FBR: Manually delete the Fedora 29 compose that is failed in Bodhi's DB

On 08/29/2018 03:26 PM, Stephen John Smoogen wrote: > Can you give me more information on what this will due, what could go > wrong and how to recover? If not I don't think I can give an answer. Bodhi has a database model called a Compose, which is used to keep track of each of its daily compose

Re: [PATCH] bodhi-pungi: specify ostree ref in config and updates for f29

Does this require a specific version of pungi? +1 if we have that version installed already... kevin signature.asc Description: OpenPGP digital signature ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send

Re: FBR: Manually delete the Fedora 29 compose that is failed in Bodhi's DB

On 08/29/2018 12:21 PM, Randy Barlow wrote: > 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

Re: FBR: Manually delete the Fedora 29 compose that is failed in Bodhi's DB

On Wed, 29 Aug 2018 at 15:21, Randy Barlow wrote: > 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

Re: Freeze Break: some more bodhi config for f29

+1 after review On Wed, 29 Aug 2018 at 14:07, Kevin Fenzi wrote: > > 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 > > +++

FBR: Manually delete the Fedora 29 compose that is failed in Bodhi's DB

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() >>>

Re: [PATCH] bodhi-pungi: specify ostree ref in config and updates for f29

Forgot to prefix with FBR, please review. This should fix: https://pagure.io/dusty/failed-composes/issue/714 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to

[PATCH] bodhi-pungi: specify ostree ref in config and updates for f29

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

suggested patch for review - issue 7158

As discussed in infra meeting 16 aug around the 14:30 mark regarding Issue #7158: Planet Fedora doesn't have a valid certificate . I created

Re: Freeze Break: some more bodhi config for f29

On 08/29/2018 02:07 PM, Kevin Fenzi wrote: > Also we need to restart fedmsg-hub on bodhi-backend01 for this and other > things to take effect. > > +1s? My vote doesn't count, but I support this ☺ signature.asc Description: OpenPGP digital signature

Freeze Break: some more bodhi config for f29

> 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 = >

Re: FBR: hotfix - Don't clean old mashes

On 08/29/2018 11:43 AM, Randy Barlow wrote: > -clean_old_mashes.remove_old_composes() OK, this is now in place on backend01 - Mohan if you resume the failed mash I think it'll succeed now. I am preparing a better fix upstream today: https://github.com/fedora-infra/bodhi/issues/2561

Re: FBR: hotfix - Don't clean old mashes

LGTM +1 On Wed, Aug 29, 2018 at 12:27 PM Kevin Fenzi wrote: > +1 and we can think about this and revisit after freeze. > > kevin > > ___ > infrastructure mailing list -- infrastructure@lists.fedoraproject.org > To unsubscribe send an email to >

Re: FBR : To fix rawhide sync location

On 08/29/2018 07:45 AM, Mohan Boddu wrote: > Yeah, good catch by Dusty. > > Hopefully, this is the right thing to do: > > diff --git a/roles/bodhi2/backend/files/new-updates-sync > b/roles/bodhi2/backend/files/new-updates-sync > index e625f50..468d269 100755 > ---

Re: FBR: hotfix - Don't clean old mashes

+1 and we can think about this and revisit after freeze. kevin signature.asc Description: OpenPGP digital signature ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to

Fedora 29 Beta Freeze now in effect

(sorry this email was delayed, it didn't seem to send yesterday when I thought I sent it). Greetings. we are now in the infrastructure freeze leading up to the Fedora 29 Beta release. This is a pre release freeze. We do this to ensure that our infrastructure is stable and ready to release the

Re: FBR: hotfix - Don't clean old mashes

On 08/29/2018 11:43 AM, Randy Barlow wrote: > 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 >

FBR: hotfix - Don't clean old mashes

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 ---

Re: FBR : To fix rawhide sync location

Yeah, good catch by Dusty. Hopefully, this is the right thing to do: diff --git a/roles/bodhi2/backend/files/new-updates-sync b/roles/bodhi2/backend/files/new-updates-sync index e625f50..468d269 100755 --- a/roles/bodhi2/backend/files/new-updates-sync +++

Re: FBR : To fix rawhide sync location

-1 sorry.. dusty pointed out that the join will create /rawhide/Everything/os/{arch} versus /rawhide/Everything/{arch}/os On Wed, 29 Aug 2018 at 10:14, Stephen John Smoogen wrote: > > +1 so we can get our rawhide out of rawhide > On Wed, 29 Aug 2018 at 10:09, Mohan Boddu wrote: > > > > Fix for

Re: FBR : To fix rawhide sync location

+1 so we can get our rawhide out of rawhide On Wed, 29 Aug 2018 at 10:09, Mohan Boddu wrote: > > 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 >

FBR : To fix rawhide sync location

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

Re: FBR: workaround for #7194

On 08/29/2018 09:58 AM, Randy Barlow wrote: > On 08/29/2018 09:57 AM, Randy Barlow wrote: >> The number is not specified, so it will also change for when Bodhi calls it. > > Ugh, which actually means it won't work. > can we not just do a small patch that removes the call to clean-old-mashes

Re: FBR: workaround for #7194

On 08/29/2018 09:57 AM, Randy Barlow wrote: > The number is not specified, so it will also change for when Bodhi calls it. Ugh, which actually means it won't work. signature.asc Description: OpenPGP digital signature ___ infrastructure mailing list

Re: FBR: workaround for #7194

On 08/29/2018 09:56 AM, Dusty Mabe wrote: > So basically the solution is to run clean_old_mashes.py as root and change > it so that it deletes "more than" what the bodhi run will delete when it runs > as non-root, thus rendering the bodhi run clean_old_mashes.py as a no-op ? Yes. > Is the number

Re: FBR: workaround for #7194

On 08/29/2018 09:19 AM, Randy Barlow wrote: > 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

Re: FBR: workaround for #7194

On 08/29/2018 09:19 AM, Randy Barlow wrote: > Basically, the current script deletes the most recent 10. Correction: the script deletes *all but* the most recent 10. signature.asc Description: OpenPGP digital signature ___ infrastructure mailing list

FBR: workaround for #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

Re: FBR: Autosigning for post bodhi activation of F29

+1 though I'd like it moved to the correct section ("Gated bodhi updates"), but I'll merge it so things get signed at least. On Tue, 28 Aug 2018 at 23:19, Kevin Fenzi wrote: > > +1 > > kevin > > ___ > infrastructure mailing list --