Introducing Luiz Carvalho

Hi all, Just an FYI - I've moved off of the Factory 2 team inside Red Hat to take a different role in the internal devops organization there. Luiz Carvalho (lucarval in both FAS and irc) takes my place leading the Factory 2 team! He's a good point of contact for greenwave, MBS, ODCS and

Re: FBR - Upgrade MBS

On Fri, Sep 07, 2018 at 03:42:06PM -0400, Ralph Bean wrote: > I'd like to upgrade MBS on either Monday or Tuesday of next week to > module-build-service-2.6.0-1.el7 and libmodulemd-1.6.3-2.el7. > > - https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-0a7da752

FBR - Upgrade MBS

I'd like to upgrade MBS on either Monday or Tuesday of next week to module-build-service-2.6.0-1.el7 and libmodulemd-1.6.3-2.el7. - https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-0a7da7520d - https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2018-ee8aeba3a6 There is no database

Re: FBR: Greenwave config update for F29

LGTM. Easy to roll back if it is incorrect. +1 On Tue, Aug 28, 2018 at 10:05:08AM -0400, Mohan Boddu wrote: > diff --git a/roles/openshift-apps/greenwave/templates/configmap.yml > b/roles/openshift-apps/greenwave/templ > index dd297c4..694ca3c 100644 > ---

Re: Fwd: Red Hat bugzilla upgrade coming -- test now!

Zach Villers > z...@mailup.net > > On Mon, Jun 25, 2018, at 9:25 AM, Ralph Bean wrote: > > FWIW, there's a change to the way messaging works with BZ5. > > > > - Messages are published to a different queue. Someone will need to > > update bugzilla2fedmsg to pull from th

Fwd: Red Hat bugzilla upgrade coming -- test now!

FWIW, there's a change to the way messaging works with BZ5. - Messages are published to a different queue. Someone will need to update bugzilla2fedmsg to pull from the new right place. - The message format changes, but I think it may only be additive. Someone should verify that we don't need

Re: Modularity WG + f2 + Infra

On Tue, May 15, 2018 at 05:01:56PM -0700, Kevin Fenzi wrote: > On 05/15/2018 08:08 AM, Randy Barlow wrote: > > Greetings! > > > > At the hackathon we did recently, we talked about the need for one of us > > to attend the Modularity WG meetings so we could be more aware of what > > work is coming

[release] pdc-updater: 0.9.2

A new release of pdc-updater is out, fixing a bug in the retirement handler. https://pagure.io/fedora-infrastructure/issue/6928 0.9.2 - Pull Requests - #86, Merge pull request #86 from fedora-infra/dont-overwrite https://github.com/fedora-infra/pdc-updater/pull/86 Commits - 65ebd4ad9

Re: Bodhi 3.7.0-0.0.beta deployed to stg

On Wed, May 09, 2018 at 12:12:50PM -0400, Randy Barlow wrote: > On 05/09/2018 12:07 PM, Randy Barlow wrote: > > Aaand it also doesn't work in production. I tested the Greenwave API > > just yesterday and it did return the data that Bodhi looks for. Today > > the exact same query omits the

Re: FBR: no CI requirements for modules

Thanks! This is done now: https://greenwave-web-greenwave.app.os.fedoraproject.org/api/v1.0/policies I fixed two other little things while I was in there: - https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=01d70107fca595715931861e80a7e642f9df191b -

FBR: no CI requirements for modules

Discussed in #fedora-admin just now. Modules are configure to require some test cases that never actually get run for them. This patch should treat them instead like we do epel: no CI requirements. Any +1s? diff --git a/roles/openshift-apps/greenwave/templates/configmap.yml

Re: FBR MBS: Fix traceback when reusing components from module build with different buildrequires.

+1 here too. It's easy to revert by downgrading the rpm if it blows up. On Fri, Apr 20, 2018 at 11:42:33AM +0200, Mikolaj Izdebski wrote: > +1 > > On 04/20/2018 08:36 AM, Jan Kaluža wrote: > > Hi, > > > > this is FBR to fix MBS traceback which prevents builds of modules in > > situation when

Re: any infra apprentices looking for a challenge?

On Sun, Feb 25, 2018 at 12:37:36PM -0500, Dusty Mabe wrote: > > > On 02/23/2018 01:38 PM, Pierre-Yves Chibon wrote: > > On Fri, Feb 23, 2018 at 05:14:38PM +, ajay vembu wrote: > >>Hi Dusty, > >>I will start working on it. I will let you know if I any queries.  > > > > Thanks for

MBS disk usage

Way back in May some of us were in Raleigh for a Hackathon: https://fedoraproject.org/wiki/CI_and_Infrastructure_Hackathon_2017 There, we talked about the MBS and wondered what kind of new storage requirements it would impose on koji. We all worried about it, but we didn't have numbers to figure

Re: [PATCH] start running f27 atomic/cloud pungi runs

+1 here too. ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: FBR: Modules and the package list

Thanks! Applied: https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=fe795ff8de2615b58a84ef7d80a919a5dad26304 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to

FBR: Modules and the package list

Karsten Hopp reported an issue with the MBS that his module builds of modules/krb5 and modules/udisks2 failed, because the MBS failed to tag them into f27-modular-updates-candidate at the end of the build. The module names weren't in the pkg list. I've added them directly to get him going again,

[release] pdc-updater: 0.6.3

Just a few small bugfixes to pdc-updater here. 0.6.3 - Pull Requests - (@ralphbean) #73, Ignore modules in the build state. https://github.com/fedora-infra/pdc-updater/pull/73 - (@hanzz) #74, Use different way to call PDC API to workaround 404 bug for valid modules in PDC.

Re: whatcanidoforfedora.org is back

Oh, I wonder how that worked before. Hm.. It looks like the old server from openshift would automatically redirect to /en/ if no language was specified. https://github.com/fedora-infra/asknot-ng/blob/develop/.openshift/diy/pythonserver.py ___

whatcanidoforfedora.org is back

http://whatcanidoforfedora.org is back (the dns change is still propagating). Patrick and I set up an ansibilized cronjob on sundries01 to build it and sync it out to the proxies, similar to how our other websites are built. Ricky's going to proceed with looking at how to auto-build it in

Freshmaker RFR

Hey all, Just like in for the ODCS RFR[1], I'm sending out a ping here about the Freshmaker RFR: https://pagure.io/fedora-infrastructure/issue/6183#comment-471098 I tried to put a bunch of context about what it is and vaguely how it works in the proposed SOP:

ODCS RFR

Hey all, I had a chat with Patrick yesterday and walked through the various parts of the RFR process that my team has done a less than great job of following. I never built up a good habit of following the RFR process to the letter. Sorry for this. Will try to do a better job. Patrick put

Re: FBR: if you liked it then you should've put a lock on it...

Applied here: http://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=aab2ea4590853acb8f631f4fae293e03df50e6cb ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to

Re: FBR - a timeout for the koji pkglist sync script

Applied: https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=18b7ea4435e2a28b65fae2dc9161900d7e961a1e ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to

FBR - a timeout for the koji pkglist sync script

Mohan and Matt found yesterday that the koji pkglist sync script was hung (for two hours) waiting on a koji query. We looked today, and found that the default timeout for koji requests is 12 hours! (whee!) Here's a patch to that script that sets a timeout of 10 minutes which, based on a reading

Re: FBR: if you liked it then you should've put a lock on it...

> How long is it taking to do a sync? I'm not sure. Patrick noticed it in #fedora-noc. > And would it be better to schedule the cron job to be non-daily in that case? Possibly, yes. (Likely still good to also put a lock on it). ___ infrastructure

FBR: if you liked it then you should've put a lock on it...

... or even if you didn't like it, it still probably needs a lock. /usr/local/bin/pagure-sync-bugzilla.py takes more than 24 hours to run, and it doesn't have a lock wrapper on it. It needs one. diff --git a/roles/distgit/pagure/tasks/main.yml b/roles/distgit/pagure/tasks/main.yml

Re: FBR: MBS upgrade

OK, this is all done and upgrade and tested as far as I can test it. My build of the `testmodule` module succeeded. https://mbs.fedoraproject.org/module-build-service/1/module-builds/953 ___ infrastructure mailing list --

Re: FBR: MBS upgrade

> That is a major code change on a Friday. What is the DB upgrade parts > and if there are further changes/problems what is the backout plan? The db change is here: https://pagure.io/fm-orchestrator/pull-request/686#_1,18 Two new added columns. The MBS (like many of our other apps) uses

FBR: MBS upgrade

Hi, I'd like to upgrade the MBS to: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2017-1db0646bc6 In particular, the bit about "Wait for components to be tagged also in final tag before marking module as done. This should fix an issue for the F27 compose." is important. See

Re: Bodhi + Modules (not quite an FBR, just yet)

New news: the Server SIG decided to go with a traditional release for F27: https://meetbot.fedoraproject.org/fedora-meeting-1/2017-09-12/serversig.2017-09-12-20.00.html - They still want to do a non-blocking modular release on the side (kind of like boltron). - We will still want/need to have

Bodhi + Modules (not quite an FBR, just yet)

This came up in the FESCo meeting today. https://github.com/fedora-infra/bodhi/issues/1795 In my last discussions with Randy, we were planning on merging, releasing, and deploying the modular bodhi masher work after Beta freeze thawed - but FESCo would rather see proof of it before freeze is up.

[release] pdc-updater: 0.6.0

A new pdc-updater release! There are a few bugfixes related to the MBS, but crucially there is a new handler for propagating retirement: When a `dead.package` file gets committed, the code here (on pdc-backend0*) will update the EOL of that branch in PDC, indicating retirement. 0.6.0 -

Re: Duplicates in package owner alias cronjob?

Fixed in https://infrastructure.fedoraproject.org/cgit/ansible.git/commit/?id=24141e596b989de79c04111291aab09effe49580 ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to

Duplicates in package owner alias cronjob?

I'm confused about something. Can any postfix experts help debug? On Friday I put a new package-owner-alias cronjob in place on bastion (that Matt Prahl wrote). It generates the package owner list from pagure over dist-git instead of generating it from pkgdb.

Re: [PATCH] F26 final 0-day release actions

LGTM. ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: Fedora 26 Final Freeze now in effect

On Wed, Jun 28, 2017 at 08:20:29AM -0600, Kevin Fenzi wrote: > On 06/28/2017 02:57 AM, Pierre-Yves Chibon wrote: > > > I did not realize this before, but this will impact the decommissioning of > > pkgdb. > > The idea was to deploy pagure on dist-git on July 5th and deprecate pkgdb on > > July

Re: FBR: Add CSS handling to Taskotron artifacts serving

On Fri, Jun 02, 2017 at 10:06:56AM -0600, Tim Flink wrote: > The modularity-testing-framework tests use avocado to output nice HTML > reports but due to the way that we store and serve the artifacts, the > css doesn't load properly. An example (that should work post-fix) is: > >

Re: FBR: Add deprecation banner to pkgdb in prod

Thanks, this is done now: https://admin.fedoraproject.org/pkgdb signature.asc Description: PGP signature ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to

FBR: Add deprecation banner to pkgdb in prod

This just got approved in FESCo today. I'd like to manually apply this patch to the pkgdb web nodes in prod: https://github.com/fedora-infra/pkgdb2/pull/415 It's a template and css change that adds a banner informing packagers of the pending plans for:

waiverdb in os.fedoraproject.org (prod)?

Cheers on os.stg.fedoraproject.org! I'd love to have waiverdb[1] be the first app on os.fedoraproject.org once it is ready. Do you guys have any estimates of when we could start messing with that in both stg and prod? (Maybe we could help you work out kinks if we can try deploying to

Re: Service account for automated rebuilds?

On Wed, May 03, 2017 at 02:35:20PM -0400, Ralph Bean wrote: > Hey all, > > For the automated rebuilds work[1][2], we're going to need a service > account with rights to do various things (only in staging for now). > For container rebuilds, it will need to be able to request new OS

Re: Service account for automated rebuilds?

CC'ing the rel-eng list for visibility. On Wed, May 03, 2017 at 02:35:20PM -0400, Ralph Bean wrote: > Hey all, > > For the automated rebuilds work[1][2], we're going to need a service > account with rights to do various things (only in staging for now). > For container rebuild

Service account for automated rebuilds?

Hey all, For the automated rebuilds work[1][2], we're going to need a service account with rights to do various things (only in staging for now). For container rebuilds, it will need to be able to request new OSBS builds via koji. For module rebuilds, it will need to be able to commit to

Re: The future of pkgdb

On Tue, Apr 25, 2017 at 01:36:50PM -0600, Kevin Fenzi wrote: > On 04/25/2017 08:23 AM, Pierre-Yves Chibon wrote: > ...snip... > > Now going through each of the requirements listed above > > - Store point of contact for a package (default assignee on bugzilla) > > - we could use the first

Re: The future of pkgdb

On Tue, Apr 25, 2017 at 02:31:19PM -0400, Randy Barlow wrote: > On Tue, 2017-04-25 at 16:23 +0200, Pierre-Yves Chibon wrote: > > - Store point of contact for a package (default assignee on bugzilla) > >   - we could use the first committer, alphabetically > >   - we could use the 'owner', but we

Re: The future of pkgdb

On Tue, Apr 25, 2017 at 07:59:46PM +0200, Mikolaj Izdebski wrote: > On 04/25/2017 07:48 PM, Ralph Bean wrote: > > On Tue, Apr 25, 2017 at 06:46:40PM +0200, Mikolaj Izdebski wrote: > >> On 04/25/2017 04:23 PM, Pierre-Yves Chibon wrote: > >>> - Store koshei in

Re: The future of pkgdb

On Tue, Apr 25, 2017 at 07:56:06PM +0200, Michael Šimáček wrote: > > > On 2017-04-25 19:48, Ralph Bean wrote: > >On Tue, Apr 25, 2017 at 06:46:40PM +0200, Mikolaj Izdebski wrote: > >>On 04/25/2017 04:23 PM, Pierre-Yves Chibon wrote: > >>>- Store kos

Re: The future of pkgdb

On Tue, Apr 25, 2017 at 06:46:40PM +0200, Mikolaj Izdebski wrote: > On 04/25/2017 04:23 PM, Pierre-Yves Chibon wrote: > > - Store koshei integration flag > > - store this in a yaml/toml file in the dist-git repo > > - let the consumers > > - do an http request to retrieve the file > >

[release] pdc-updater: 0.5.5

New release includes a fix to support the module build service. The koji tag names we were constructing were too long. 0.5.5 - Pull Requests - #53, Merge pull request #53 from hanzz/module-hash https://github.com/fedora-infra/pdc-updater/pull/53 Commits - b0f14d1f8 Use hash instead of

Re: WhatCanIDoForFedora Hosting Server

On Tue, Apr 04, 2017 at 09:57:15AM -0600, InvalidPath wrote: > On Tue, Apr 4, 2017 at 9:27 AM, Stephen John Smoogen <smo...@gmail.com> > wrote: > > > This was a project that Ralph Bean started to try and get an idea of > > what it could be. It seems to be running

Re: FBR, check_modulemd check for taskotron!

On Fri, Mar 24, 2017 at 01:01:16PM -0600, Kevin Fenzi wrote: > +1 here > > kevin Thanks! All done and running. signature.asc Description: PGP signature ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an

FBR, check_modulemd check for taskotron!

Hey all, I'm seeking a FBR to enable a new taskotron check in production. It's not urgent (nothing will be blocked without it). It would just be nice to have. Tim Flink says in channel that "it's not a risky or major change". Backing it out would involve reverting that conditional in

FBR: PDC update

Hi all, I'd like to update: - PDC to python-pdc-1.2.0-8.git.30.gacf661f (f25-infra) on pdc-web0* - pdc-updater to pdc-updater-0.5.4-1 (epel7-infra) on pdc-backend0* There are two changes that come with this: - First, there is a new field in the productmd information produced by pungi which

Bugzilla upgrade sometime in March, maybe.

FYI, there's an upgrade to Bugzilla 5 in the works. There's no exact date yet, but it looks like March is the current target. It occurs to me that we'll be in F26 Alpha freeze then, so it may be good to try and figure out what adjustments need to be made before then. This was brought to my

Re: Dreams and Plans and Ideas for 2017

On Wed, Jan 04, 2017 at 10:51:08AM -0700, Kevin Fenzi wrote: > Greetings and happy new year to everyone. > > I'd like to divide this email up into 2 parts: > > Firstly, what all do we want to get done in the next 2 months? > The end of Feb is the end of the Red Hat Fiscal year and many of us >

[release] fedmsg: 0.18.1

This release primarily contains Patricks' bugfix, found this morning. 0.18.1 -- Pull Requests - (@ralphbean) #390, Drop old testcases against old python-six. https://github.com/fedora-infra/fedmsg/pull/390 - (@puiterwijk) #393, Only check for stomp messages after we decoded any

[release] fedmsg: 0.18.0

Hi all, I've cut a new release of fedmsg upstream and will be packaging it for Fedora and EPEL. There's nothing in this release that needs to be rolled out in the infra environment imminently. This email is just to let you know that the release if available for when we next do mass updates.

Re: Triage of fedmsg issues

On Wed, Nov 09, 2016 at 12:46:48PM +0100, Pierre-Yves Chibon wrote: > On Tue, Nov 08, 2016 at 08:25:45PM -0500, Ralph Bean wrote: > > On Tue, Nov 08, 2016 at 04:04:38PM +0100, Pierre-Yves Chibon wrote: > > > On Thu, Nov 03, 2016 at 09:18:43AM -0600, Kevin Fenzi wrote: > >

Re: Triage of fedmsg issues

On Tue, Nov 08, 2016 at 04:04:38PM +0100, Pierre-Yves Chibon wrote: > On Thu, Nov 03, 2016 at 09:18:43AM -0600, Kevin Fenzi wrote: > > This is likely also https://pagure.io/fedora-infrastructure/issue/4022 > > Perhaps I should close that one UPSTREAM? > > (I have no idea if it still needs fixing)

Re: [PATCH] update owner-sync-pkgdb to support the docker namespace

+1 here signature.asc Description: PGP signature ___ infrastructure mailing list -- infrastructure@lists.fedoraproject.org To unsubscribe send an email to infrastructure-le...@lists.fedoraproject.org

Re: bodhi-2.3.0-0.1.beta is deployed to staging

On Thu, Oct 20, 2016 at 03:13:35PM -0400, Randy Barlow wrote: > On Thu, 2016-10-20 at 10:07 +0530, Trishna Guha wrote: > > It would be nice if you could link to a guide on how to test Bodhi on > > staging so that I can jump in :). > > Unfortunately I don't think such a guide has been written. I

[release] pdc-updater: 0.3.0

Hey all, A new release of pdc-updater is out. There are a few bug fixes in place. PR#15 adds wholly new functionality to start modelling our dependency chain in PDC. For more information see https://fedoraproject.org/wiki/User:Ralph/Drafts/Infrastructure/Factory2/ModellingDeps I'll be

Re: Freeze break request: Add diversity-bot to ircbot.py

On Fri, Sep 02, 2016 at 02:53:45PM -0600, Kevin Fenzi wrote: > On Fri, 02 Sep 2016 16:01:23 +0100 > Clement Verna wrote: > > Sorry if I bring confusion, but I though that the freeze was over. I > > believe Kevin sent an email about this earlier this week. > > We are not in

Re: Freeze break request: Add diversity-bot to ircbot.py

On Fri, Sep 02, 2016 at 10:41:37PM +1000, Will Thames wrote: > > On 2 Sep 2016, at 18:38, Justin W. Flory wrote: > > > Hi Will, > > > > On 09/02/2016 03:15 AM, Will Thames wrote: > >> I hope the below code review is ok. I have a lot of experience with > >> Ansible, but not

Re: Breaking distgit-stg

On Tue, Jul 19, 2016 at 06:12:35PM +0200, Pierre-Yves Chibon wrote: > Good Morning Everyone, > > As part of his Google Summer of Code Vivek Anand has been working on adjusting > pagure so that it would fit our needs to run it on the top of distgit. > > All the changes have been merged now and

Re: zodbot upgraded

On Mon, Jun 27, 2016 at 04:27:59PM -0600, Kevin Fenzi wrote: > I've completed the upgrade of zodbot to limnoria. https://github.com/ProgVal/Limnoria Awesome! Thanks Kevin. :) signature.asc Description: PGP signature ___ infrastructure mailing list

Re: Systems (and ideas) for Modularity

I see that someone reorganized the demo videos on our fedorapeople space. They're in this dir now: https://fedorapeople.org/groups/modularity/sprint-5-demo/ ___ infrastructure mailing list infrastructure@lists.fedoraproject.org

Systems (and ideas) for Modularity

Hey all, The Modularity Working Group[1] is doing the "sprint" thing to organize work. We just completed a sprint, and have some demo videos up. The full list will be on youtube[2] later today, but we stage them on fedorapeople.org[3]. I wanted to point out a wiki page where we've been trying

[release] fedmsg_meta_fedora_infrastructure: 0.17.4

0.17.4 -- Pull Requests - (@ralphbean) #375, Return the package associated with a bz update. https://github.com/fedora-infra/fedmsg_meta_fedora_infrastructure/pull/375 - (@AdamWill) #376, openQA: revise meta processor for pending new message format

Re: Freeze Break request: sync up fedmsg rules

On Wed, Apr 20, 2016 at 09:54:53AM -0600, Kevin Fenzi wrote: > Greetings. > > I'd like to run: > > time ansible-playbook /srv/web/infra/ansible/master.yml -t > fedmsgdconfig,fedmsgmonitor > > ie, the fedmsgdconfig and fedmsgmonitor tags over all hosts. > > The reason is that we added a new

Re: [release] anitya: 0.9.1

On Tue, Apr 19, 2016 at 03:03:58PM +0200, Pierre-Yves Chibon wrote: > It should cut the list of failed update of ~200 projects :) Nice! :) signature.asc Description: PGP signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org

Re: PS1 configuration

On Thu, Apr 07, 2016 at 10:28:54AM -0600, Kevin Fenzi wrote: > On Wed, 6 Apr 2016 17:39:27 -0400 > Zach Villers wrote: > > > Hello infra, > > > > First apologies for blowing up your inbox with ansible commits. > > > > Second - if you have a chance, please log into these

[release] the-new-hotness: 0.7.3

0.7.3 - Pull Requests - (@phracek)#108, Fixes #107: Detect if file exists or is not empty https://github.com/fedora-infra/the-new-hotness/pull/108 - (@ralphbean) #109, Correct another instance of mis-used six.iteritems().

Re: Freeze break: buildvmhosts and buildvms reboot for multipath iscsi

On Thu, Mar 24, 2016 at 08:05:29AM -0600, Kevin Fenzi wrote: > Greetings. > > It seems that somehow our buildvmhost-10/11/12 machines are not > currently properly multipathed to the iscsi on the netapp. > > Normally, multipath means there's a number of ways to reach the iscsi > lun and the

Bugzilla+fedmsg, 2016-03-29

There's a Bugzilla outage scheduled for 00:00 2016-03-29 UTC. If everything goes to plan, bugzilla should start transmitting messages about changes to bug tickets shortly after this outage is complete. We have a mediator service running and ready that should receive those and rebroadcast them to

Re: Freeze break request: Update Autocloud for latest pungi/koji fedmsg updates

On Wed, Mar 23, 2016 at 11:11:49PM +0530, Kushal Das wrote: > Hi all, > > I am applying for a freeze break request for Autocloud project. We need > to be able to get koji build state changes from fedmsg so that we can > test F24, and rawhide Cloud/Atomic builds. The following [1] hotfix patch is

Re: Freeze break: pkgs git config

On Sun, Mar 20, 2016 at 04:38:40PM -0600, Kevin Fenzi wrote: > Greetings. > > It seems there is a fedpkg/pyrpgk update that depends on using the > namespaced (/rpms/) git checkouts. > > I'd like to apply the following to pkgs02: > > diff --git a/inventory/group_vars/pkgs

Freeze Break Request: Turn on fedmsg for PDC

We currently use a fedmsg-driven daemon to update PDC about stuff that gets composed by pungi. This patch turns on a new layer that lets PDC publish its own messages when it gets updated (the software comes with fedmsg as one of four different message-publication methods it can use, which is

Re: Freeze Break Request: Turn on fedmsg for PDC

This has been applied and is being pushed out. signature.asc Description: PGP signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Re: Freeze break: db01 tuning

On Tue, Mar 15, 2016 at 09:21:52AM -0600, Kevin Fenzi wrote: > Greetings. > > I was going to wait until after freeze to mess with the other > postgresql hosts, but then mattdm pointed out this morning that > hyperkitty is really slow currently. I'm not sure this will help, but > it really make

Re: Freeze break: do not redirect staging websites

On Mon, Mar 14, 2016 at 12:22:29PM +0100, Robert Mayr wrote: > Ok this is for staging websites, but it's a change in ansible and we change > some pre_tasks, so I ask for +1s to be sure. > > Staging websites should not redirect prerelease pages, but show them > normally (while production must

Re: Technical debt fighting week, round #2

On Wed, Mar 09, 2016 at 11:23:01AM -0500, Ralph Bean wrote: > On Tue, Mar 08, 2016 at 11:26:49AM -0500, Ralph Bean wrote: > > On Tue, Mar 08, 2016 at 05:21:20PM +0100, Pierre-Yves Chibon wrote: > > > To keep people motivated and involved, we will do a short (<15minute

Re: Freeze Break Request: Let openqa01.qa publish to the fedmsg bus

On Thu, Mar 10, 2016 at 04:56:15PM -0500, Ralph Bean wrote: > We want openqa01 to publish to the fedmsg bus (adamw's project) for some > integrations that releng/qa are working on for the release. > > The patch below does two things: > > - It whitelists the ip for openqa01 on

Freeze Break Request: Let openqa01.qa publish to the fedmsg bus

We want openqa01 to publish to the fedmsg bus (adamw's project) for some integrations that releng/qa are working on for the release. The patch below does two things: - It whitelists the ip for openqa01 on the inbound fedmsg relay. We need this since openqa01 is in the qa net, so it has to

Re: [PATCH] Fix `invalid signature!` to pagure's messages

On Wed, Mar 09, 2016 at 05:29:29PM -0500, Patrick Uiterwijk wrote: > > - Original Message - > > Pagure can send message with the topic: pagure.request.assigned.added but > > this > > is currently not allowed so we get an `invalid signature` error. > > > > Could I get a couple of +1s to

Re: Freeze break: build production websites from pagure

On Wed, Mar 09, 2016 at 10:08:58PM +0100, Robert Mayr wrote: > Recently the websites repository switched from fedorahosted to pagure and > we want to build websites now from there also for production. > Actually the websites in staging are built from pagure and we don't have > any issues so far.

Re: Freeze break: restart httpd on proxies

On Wed, Mar 09, 2016 at 01:42:19PM -0700, Kevin Fenzi wrote: > I pushed some redirects out for the websites folks yesterday before > freeze, but they aren't working right. > > I'd like to restart httpd on all the proxies to pick up these current > changes. > > ie, > > ansible -a 'systemctl

Re: Technical debt fighting week, round #2

On Tue, Mar 08, 2016 at 11:26:49AM -0500, Ralph Bean wrote: > On Tue, Mar 08, 2016 at 05:21:20PM +0100, Pierre-Yves Chibon wrote: > > To keep people motivated and involved, we will do a short (<15minutes) > > daily-meetup on #fedora-admin at 16:00 UTC. > > Feel fr

Re: Freeze Break Request: Forward pungi fedmsg messages to #fedora-releng

Thanks all! This has been applied. signature.asc Description: PGP signature ___ infrastructure mailing list infrastructure@lists.fedoraproject.org http://lists.fedoraproject.org/admin/lists/infrastructure@lists.fedoraproject.org

Freeze Break Request: Forward pungi fedmsg messages to #fedora-releng

Hi all. I think this one is the first freeze break request of the season. Cheers! We want to have messages about so-called "doomed" composes show up in #fedora-releng so people can respond to it. Value01 is frozen, but the change is simple. If something goes haywire, I can easily 'git revert'

Re: Technical debt fighting week, round #2

On Tue, Mar 08, 2016 at 05:21:20PM +0100, Pierre-Yves Chibon wrote: > To keep people motivated and involved, we will do a short (<15minutes) > daily-meetup on #fedora-admin at 16:00 UTC. > Feel free to join there as well, it will be a good place to sync up work done > and work remaining. Here are

[release] the-new-hotness: 0.7.2

A bugfix to the last release which should attach more information to bugs when rebase-helper fails to bump things. 0.7.2 - Pull Requests - (@phracek)#106, Fixes #105: Rebase helper logs https://github.com/fedora-infra/the-new-hotness/pull/106 Commits - 4f145e9c1 Fixes #105 Add

[release] bugzilla2fedmsg: 0.3.0

Almost ready here... 0.3.0 - Pull Requests - (@ralphbean) #5, Look before you leap. https://github.com/fedora-infra/bugzilla2fedmsg/pull/5 - (@ralphbean) #6, Got moved again. https://github.com/fedora-infra/bugzilla2fedmsg/pull/6 Commits - 8c0080ec9 Remove unused import.

[release] fedmsg: 0.16.4

A bugfix. Some of the py3 changes we made broke py2 behavior. 0.16.4 -- Pull Requests - (@AdamWill) #364, instead of setsockopt_string, encode topic and use setsockopt https://github.com/fedora-infra/fedmsg/pull/364 Commits - 63f6c11c4 instead of setsockopt_string, encode topic

[release] fedmsg: 0.16.3

0.16.3 -- Primarily, some python3 fixes for fedmsg.tail_messages() in here. Pull Requests - (@ralphbean) #357, Stick with alternative cache location. https://github.com/fedora-infra/fedmsg/pull/357 - (@ralphbean) #358, Remove markup stuff.

[release] fmn.web: 0.8.1

0.8.1 - Pull Requests - (@ralphbean) #73, Fix export link on filter page. https://github.com/fedora-infra/fmn.web/pull/73 Commits - ac399ed98 Fix export link on filter page. https://github.com/fedora-infra/fmn.web/commit/ac399ed98 ___

[release] fmn.consumer: 0.8.1

0.8.1 - Pull Requests - #68, Merge pull request #68 from fedora-infra/feature/selfie https://github.com/fedora-infra/fmn.consumer/pull/68 - #69, Merge pull request #69 from mattiaverga/develop https://github.com/fedora-infra/fmn.consumer/pull/69 -

[release] fmn.lib: 0.8.1

0.8.1 - Pull Requests - #60, Merge pull request #60 from fedora-infra/feature/stg-too https://github.com/fedora-infra/fmn.lib/pull/60 Commits - 6cf829cf1 Let this work in staging also. https://github.com/fedora-infra/fmn.lib/commit/6cf829cf1

[release] fmn.rules: 0.8.1

0.8.1 - Pull Requests - #70, Merge pull request #70 from fedora-infra/feature/only-taskotron https://github.com/fedora-infra/fmn.rules/pull/70 - #71, Merge pull request #71 from fedora-infra/feature/nagios

  1   2   3   >