Meeting agenda for 2020-02-20
by Stephen John Smoogen
## Preamble
The infrastructure team will be having its weekly meeting tomorrow,
2020-02-20 at 15:00 UTC in #fedora-meeting-1 on the freenode network.
We have a document at https://board.net/p/fedora-infra
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 (2020-02-20)
#meetingname infrastructure
#chair nirik pingou relrod smooge tflink cverna mizdebsk mkonecny
abompard bowlofeggs
#info Agenda is at: https://board.net/p/fedora-infra
#topic aloha
```
### Determine who the next chair is
#topic Next chair
#info magic eight ball says:
#info 2020-02-20 - bowlofeggs
#info 2020-02-27 - ???
### 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
#info Getting Started Guide:
https://fedoraproject.org/wiki/Infrastructure/GettingStarted
```
### 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 ops folks are doing a 30min ticket triage every day at 19UTC in
#fedora-admin - please join
#info Fedora Infrastructure will be moving in 2020-06 from its Phoenix
Az datacenter to one near Herndon Va. A lot of planning will be
involved on this. Please watch out for announcements on changes.
#info Old openstack cloud is being decommissioned 2020-03-01. Working
with instance owners to make sure everyone is migrated off.
#info New blog post about release-monitoring.org is now out
https://communityblog.fedoraproject.org/stories-from-the-amazing-world-of...
#info We say thank you to bowlofeggs who is leaving Red Hat for other places.
#info We say thank you to relrod who is leaving CPE to go to Ansible.
```
### 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 https://fedoraproject.org/wiki/Infrastructure/Oncall
#info nirik is oncall 2020-02-13 -> 2020-02-20
#info cverna is oncall 2020-02-20 -> 2020-02-27
#info pingou is oncall 2020-02-28 -> 2020-03-05
## .oncalltakeeu .oncalltakeus
#info Summary of last week: (from current oncall )
#info
#topic Monitoring discussion [nirik]
#info https://nagios.fedoraproject.org/nagios
#info Go over existing out items and fix
#topic Tickets discussion [nirik]
#info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket
#topic backlog discussion
#info go over our backlog and discuss and determine priority
```
Go thru each ticket one by one
### Put all topics for discussion under here
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.
4 years, 2 months
Meeting agenda 2020-02-20 15:00 UTC
by Randy Barlow
The infrastructure team will be having its weekly meeting tomorrow,
2020-02-20 at 15:00 UTC in #fedora-meeting-1 on the freenode network.
We have a document at https://board.net/p/fedora-infra
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 (2020-02-20)
#meetingname infrastructure
#chair nirik pingou relrod smooge tflink cverna mizdebsk mkonecny abompard bowlofeggs
#info Agenda is at: https://board.net/p/fedora-infra
#topic aloha
```
### Determine who the next chair is
#topic Next chair
#info magic eight ball says:
#info 2020-02-20 - bowlofeggs
#info 2020-02-27 - ???
### 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
#info Getting Started Guide: https://fedoraproject.org/wiki/Infrastructure/GettingStarted
```
### 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 ops folks are trying a 30min ticket triage every day at 19UTC in #fedora-admin
#info Fedora Infrastructure will be moving in 2020-06 from its Phoenix Az datacenter to one near Herndon Va. A lot of planning will be involved on this. Please watch out for announcements on changes.
#info Old openstack cloud is being decommissioned 2020-03-01. Working with instance owners to make sure everyone is migrated off.
#info New blog post about release-monitoring.org is now out https://communityblog.fedoraproject.org/stories-from-the-amazing-world-of...
```
### 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 https://fedoraproject.org/wiki/Infrastructure/Oncall
#info nirik is oncall 2020-02-13 -> 2020-02-20
#info cverna is oncall 2020-02-20 -> 2020-02-27
#info pingou is oncall 2020-02-28 -> 2020-03-05
## .oncalltakeeu .oncalltakeus
#info Summary of last week: (from current oncall )
#info
#topic Monitoring discussion [nirik]
#info https://nagios.fedoraproject.org/nagios
#info Go over existing out items and fix
#topic Tickets discussion [nirik]
#info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket
#topic backlog discussion
#info go over our backlog and discuss and determine priority
```
Go thru each ticket one by one
### Put all topics for discussion under here
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
4 years, 2 months
CPE Weekly: 2020-02-14
by Aoife Moloney
# CPE Weekly: 2020-02-14
Background:
The Community Platform Engineering group is the Red Hat team combining
IT and release engineering from Fedora and CentOS. Our goal is to keep
core servers and services running and maintained, build releases, and
other strategic tasks that need more dedicated time than volunteers
can give.
For better communication, we will be giving weekly reports to the
CentOS and Fedora communities about the general tasks and work being
done. Also for better communication between our groups we have
created #redhat-cpe on Freenode IRC! Please feel free to catch us
there, a mail has landed on both the CentOS and Fedora devel lists
with context here.
## Fedora Updates
### Data Centre Move
By June 15th 2020, dedicated Fedora servers will have moved to a new
data centre in Northern Virginia.
If you want to read more, check out our post on hackmd:
https://hackmd.io/@Ap8CkTlpSfmjb44UGV-kWA/rJsk7A-QL
Here are some key dates and actions we need you to know:
* On 28th Feb, the old OpenStack instance in Fedora Cloud will be retired.
* Please reach out to Kevin before 25th Feb if you need to take action
for your instance if you are an instance owner. Here is the link to
the current status: https://pagure.io/fedora-infrastructure/issue/8614
* On 13th April, the CPE team will begin to ship servers to our new
data centre - this does not affect F32 distribution or release
* From March 1st, the CPE team will begin to build the Minimum Viable
Fedora infrastructure in the new datacenter
* Between May 20th - July 1st, we will be redirecting Fedora services
to run on the 'MVF' offering to facilitate the final part of the move
and allow for re-racking and testing
* By July 1st we hope to have BAU (business as usual) for Fedora infra
### AAA Replacement
This project is replacing our old existing fas (fedora account system)
with a new freeipa based system.
* Check out our blog on the teams progress to date!
* You can also see our jira board for tickets we are working on
* And we have an IRC channel - #fedora-AAA
* We are currently working on the FreeIPA API integration and the
folks at FreeIPA have been really helpful so far to work with
### CI/CD
* The team have been trying to get a local instance of Koji running this week
* They are investigating different algorithms that could help generate
the next release if a package based on its git history.
* Monitoring-gating is being deployed in OpenShift in staging
### Sustaining Team
* The team meets daily @ 1900 UTC in #fedora-admin on IRC
* The priority work is:
** Fedora 32
** Assisting with technical debt to facilitate the colo move
** mbbox upgrading
** CentOS CI OpenShift upgrading
* The team also have a public thread on knowledge sharing,
https://lists.fedoraproject.org/archives/list/infrastructure@lists.fedora...
so take a look!
## Docs
* Merged https://pagure.io/fedora-docs/quick-docs/pull-request/175
* Merged https://pagure.io/fedora-docs/quick-docs/pull-request/174
* Merged https://pagure.io/fedora-docs/quick-docs/pull-request/173
* Merged https://pagure.io/fedora-docs/quick-docs/pull-request/167
* Reviewed https://pagure.io/fedora-docs/install-guide/pull-request/40
* Also work underway on CentOS 8.1 docs
### Misc Updates
* The team are also working on creating Fedora infra application map -
stay tuned for the publication soon!
* keys.fedoraproject.org has been turned off
* boot.fedoraproject.org will be retired this week
* Certs have been changed to letsencrypt for fedorahosted/fedoracommunity
* Moved Koji calls to a backend task worker in Bodhi:
https://github.com/fedora-infra/bodhi/issues/3061
* kdreyer's playbook repo has been integrated:
https://pagure.io/koji-vagrant/pull-request/1
* Testing dist-git repo as a submodule has been added:
https://pagure.io/koji-vagrant/pull-request/2
* Ticket in Monitor-Gating has been reviewed:
https://pagure.io/fedora-ci/monitor-gating/pull-request/8
## CentOS Updates
### CentOS
* Tuning/adding more mirrorlist servers due to EC2/AWS change from last week
* Updates are really faster now for CentOS users in AWS/EC2 (more
than 100TiB of updated packages served internally with a 98.33% ratio
served from cache, so faster than ever)
* Moving data from CentOs Infra and switching to a new solution for
backup for infra:
* https://github.com/CentOS/ansible-role-centos-backup/
* https://github.com/CentOS/ansible-role-restic
* VDO (https://access.redhat.com/documentation/en-us/red_hat_enterprise_linux/7/...)
* Investigating how to incorporate CentOS auth into the new AAA solution
* We'll need proper communication plan to ask everybody to get a
FAS account when we'll migrate
### CentOS Stream
* The CPE team are collaborating with the Packit team internally to
develop a workflow for contributor patches
* We are working towards demoing a contributor patch from submission
to end for Red Hat Summit in April!
As always, feedback is welcome, and we will continue to look at ways
to improve the delivery and readability of this weekly report.
Have a great weekend!
Aoife
--
Aoife Moloney
Product Owner
Community Platform Engineering Team
Red Hat EMEA
Communications House
Cork Road
Waterford
4 years, 2 months
When adding hosts to ansible please first update DNS
by Stephen John Smoogen
When bringing up a new host,
1. Edit the appropriate dns file in the Fedora Infrastructure DNS
repository.
2. Commit the changes and wait for them to sync out to dns.
3. Test that the hostname and ip address match.
4. Add the hostname to the ansible inventory file in the appropriate group.
5. Continue the deployment from then on.
Because ip addresses can change, and we do not have time to fix it in
multiple places, we are asking that no 'naked' ip addresses be used in the
ansible inventory from now on. We will be working on removing all entries
by Wednesday and after that any 'naked' ip address commit to the inventory
will be reverted.
--
Stephen J Smoogen.
4 years, 2 months
fedora-messaging/rabbitmq in staging cluster rebuild tonight
by Kevin Fenzi
Greetings.
Just a heads up that later today I intend to reinstall the staging
rabbitmq cluster with rhel8 and a newer rabbitmq.
(in the early hours of 2020-02-14 UTC).
Playbooks then will be run to resetup users and queues.
Abompard will check over everything when he gets in the first thing in
his morning tomorrow, so any problems will hopefully be not too many
hours long.
This upgrade should allow us some nice new features and if all looks
well we will schedule a time to do production as well.
Just wanted to let everyone know in case you saw alerts or missing
messages later today.
Thanks for your patience.
kevin
4 years, 2 months
datacenter=aws
by Miroslav Suchý
I am deploying Copr machines in AWS from our ansible.git and I just learned that
https://infrastructure.fedoraproject.org/pub/fedora/linux/
is not reachable from AWS.
I took the initiative and added new semantic to variable 'datacenter'.
When it is set to
datacenter=aws
then base role does not modify fedora*.repo
It is probably needed for centos and other, but I needed just this.
Miroslav
-------- Přeposlaná zpráva --------
Předmět: [ansible] do not modify fedora*.repo when deploying in AWS
Datum: Fri, 14 Feb 2020 13:27:04 +0000 (UTC)
Od: Miroslav Suchý <msuchy(a)fedoraproject.org>
Komu: sysadmin-members(a)fedoraproject.org
commit 034810b13164ab68b93a6aa941ec0ceb1ac2e7a1
Author: Miroslav Suchý <msuchy(a)redhat.com>
Date: Fri Feb 14 14:26:31 2020 +0100
do not modify fedora*.repo when deploying in AWS
inventory/host_vars/18.215.229.156 | 1 +
tasks/yumrepos.yml | 8 ++++----
2 files changed, 5 insertions(+), 4 deletions(-)
---
diff --git a/inventory/host_vars/18.215.229.156 b/inventory/host_vars/18.215.229.156
index c0b99b8..f0f7d91 100644
--- a/inventory/host_vars/18.215.229.156
+++ b/inventory/host_vars/18.215.229.156
@@ -2,6 +2,7 @@
ansible_ssh_user: fedora
ansible_become_user: root
ansible_become: yes
+datacenter: aws
#instance_type: t3a.small
#image: "{{ fedora31_x86_64 }}"
#keypair: fedora-admin-20130801
diff --git a/tasks/yumrepos.yml b/tasks/yumrepos.yml
index fa64bb6..b7ef54b 100644
--- a/tasks/yumrepos.yml
+++ b/tasks/yumrepos.yml
@@ -54,7 +54,7 @@
- fedora.repo
- fedora-updates.repo
- fedora-updates-testing.repo
- when: ansible_distribution == 'Fedora' and not inventory_hostname.startswith(('buildvm-s390x', 'buildvm-ppc64le'))
and not inventory_hostname.startswith('rawhide-test')
+ when: ansible_distribution == 'Fedora' and not inventory_hostname.startswith(('buildvm-s390x', 'buildvm-ppc64le'))
and not inventory_hostname.startswith('rawhide-test') and datacenter != "aws"
tags:
- config
- packages
@@ -66,7 +66,7 @@
- fedora-modular.repo
- fedora-updates-modular.repo
- fedora-updates-testing-modular.repo
- when: ansible_distribution == 'Fedora' and not inventory_hostname.startswith('rawhide-test') and not
inventory_hostname.startswith(('buildvm-s390x', 'buildvm-ppc64le'))
+ when: ansible_distribution == 'Fedora' and not inventory_hostname.startswith('rawhide-test') and not
inventory_hostname.startswith(('buildvm-s390x', 'buildvm-ppc64le')) and datacenter != "aws"
tags:
- config
- packages
@@ -78,7 +78,7 @@
- fedora.repo
- fedora-updates.repo
- fedora-updates-testing.repo
- when: ansible_distribution == 'Fedora' and (ansible_architecture == 'ppc64' or ansible_architecture == 'ppc64le' or
ansible_architecture == 's390x')
+ when: ansible_distribution == 'Fedora' and (ansible_architecture == 'ppc64' or ansible_architecture == 'ppc64le' or
ansible_architecture == 's390x') and datacenter != "aws"
tags:
- config
- packages
@@ -90,7 +90,7 @@
- fedora-modular.repo
- fedora-updates-modular.repo
- fedora-updates-testing-modular.repo
- when: ansible_distribution == 'Fedora' and ansible_distribution_major_version >= 29 and (ansible_architecture ==
'ppc64le' or ansible_architecture == 's390x')
+ when: ansible_distribution == 'Fedora' and ansible_distribution_major_version >= 29 and (ansible_architecture ==
'ppc64le' or ansible_architecture == 's390x') and datacenter != "aws"
tags:
- config
- packages
4 years, 2 months
Fedora Infrastructure Meeting Agenda for 2020-02-13
by Stephen John Smoogen
## Preamble
The infrastructure team will be having its weekly meeting tomorrow,
2020-02-13 at 15:00 UTC in #fedora-meeting-1 on the freenode network.
We have a document at https://board.net/p/fedora-infra
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 (2020-02-13)
#meetingname infrastructure
#chair nirik pingou relrod smooge tflink cverna mizdebsk mkonecny abompard
bowlofeggs
#info Agenda is at: https://board.net/p/fedora-infra
#topic aloha
```
### Determine who the next chair is
#topic Next chair
#info magic eight ball says:
#info 2020-02-13 - smooge
#info 2020-02-20 - bowlofeggs
#info 2020-02-27 - ???
### 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
#info Getting Started Guide:
https://fedoraproject.org/wiki/Infrastructure/GettingStarted
```
### 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 ops folks are trying a 30min ticket triage every day at 19UTC in
#fedora-admin
#info Fedora Infrastructure will be moving in 2020-06 from its Phoenix Az
datacenter to one near Herndon Va. A lot of planning will be involved on
this. Please watch out for announcements on changes.
#info Fedora 32 has been branched from rawhide.
#info
```
### 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 https://fedoraproject.org/wiki/Infrastructure/Oncall
#info smooge is oncall 2020-02-06 -> 2020-02-13
#info nirik is oncall 2020-02-13 -> 2020-02-20
#info cverna is oncall 2020-02-20 -> 2020-02-27
#info ??? is oncall 2020-02-27 -> 2020-03-05
## .oncalltakeeu .oncalltakeus
#info Summary of last week: (from current oncall )
#info DNS broke on 2020-02-11 due to signing problems.
#topic Monitoring discussion [nirik]
#info https://nagios.fedoraproject.org/nagios
#info Go over existing out items and fix
#topic Tickets discussion [nirik]
#info https://pagure.io/fedora-infrastructure/report/Meetings%20ticket
#topic backlog discussion
#info go over our backlog and discuss and determine priority
```
Go thru each ticket one by one
### Put all topics for discussion under here
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.
4 years, 2 months
[PATCH] Drop myself from various infra roles
by Jeremy Cline
I requested that my infrastructure access be removed since I don't use
it anymore, so drop myself from various playbooks and configurations. I
can't do anything with the warning emails anyway.
---
playbooks/groups/os-cluster.yml | 1 -
playbooks/openshift-apps/messaging-bridges.yml | 1 -
.../templates/fedora-messaging/copr_messaging.toml | 2 +-
.../openshift-apps/messaging-bridges/templates/amqp-to-zmq.toml | 2 +-
.../messaging-bridges/templates/verify-missing.toml | 2 +-
.../openshift-apps/messaging-bridges/templates/zmq-to-amqp.toml | 2 +-
6 files changed, 4 insertions(+), 6 deletions(-)
diff --git a/playbooks/groups/os-cluster.yml b/playbooks/groups/os-cluster.yml
index ca10178dc..68aa77311 100644
--- a/playbooks/groups/os-cluster.yml
+++ b/playbooks/groups/os-cluster.yml
@@ -235,7 +235,6 @@
- cverna
- dcallagh
- gnaponie
- - jcline
- lholecek
- misc
- mizdebsk
diff --git a/playbooks/openshift-apps/messaging-bridges.yml b/playbooks/openshift-apps/messaging-bridges.yml
index feb126533..df19b180b 100644
--- a/playbooks/openshift-apps/messaging-bridges.yml
+++ b/playbooks/openshift-apps/messaging-bridges.yml
@@ -118,7 +118,6 @@
description: "ZeroMQ <-> AMQP bridges"
appowners:
- abompard
- - jcline
- role: openshift/secret-file
app: messaging-bridges
diff --git a/roles/copr/frontend-cloud/templates/fedora-messaging/copr_messaging.toml b/roles/copr/frontend-cloud/templates/fedora-messaging/copr_messaging.toml
index 089d71537..b5bf3df71 100644
--- a/roles/copr/frontend-cloud/templates/fedora-messaging/copr_messaging.toml
+++ b/roles/copr/frontend-cloud/templates/fedora-messaging/copr_messaging.toml
@@ -17,7 +17,7 @@ app = "Example Application"
app_url = "https://github.com/fedora-infra/fedora-messaging"
# Contact emails for the maintainer(s) of the consumer - in case the
# broker admin needs to contact them, for e.g.
-app_contacts_email = ["jcline(a)fedoraproject.org"]
+app_contacts_email = []
[exchanges."amq.topic"]
type = "topic"
diff --git a/roles/openshift-apps/messaging-bridges/templates/amqp-to-zmq.toml b/roles/openshift-apps/messaging-bridges/templates/amqp-to-zmq.toml
index 3bbd97494..25db1104d 100644
--- a/roles/openshift-apps/messaging-bridges/templates/amqp-to-zmq.toml
+++ b/roles/openshift-apps/messaging-bridges/templates/amqp-to-zmq.toml
@@ -48,7 +48,7 @@ filters = ["ratelimit"]
formatter = "simple"
mailhost = "bastion"
fromaddr = "fedmsg-migration-tools(a)fedoraproject.org"
-toaddrs = ["jcline(a)fedoraproject.org", "abompard(a)fedoraproject.org"]
+toaddrs = ["abompard(a)fedoraproject.org"]
subject = "ERROR: fedmsg-migration-tools amqp-to-zmq bridge"
[log_config.loggers.fedora_messaging]
level = "INFO"
diff --git a/roles/openshift-apps/messaging-bridges/templates/verify-missing.toml b/roles/openshift-apps/messaging-bridges/templates/verify-missing.toml
index be238d5e6..1d847beea 100644
--- a/roles/openshift-apps/messaging-bridges/templates/verify-missing.toml
+++ b/roles/openshift-apps/messaging-bridges/templates/verify-missing.toml
@@ -60,7 +60,7 @@ formatter = "simple"
filters = ["ratelimit"]
mailhost = "bastion"
fromaddr = "fedmsg-migration-tools(a)fedoraproject.org"
-toaddrs = ["jcline(a)fedoraproject.org", "abompard(a)fedoraproject.org"]
+toaddrs = ["abompard(a)fedoraproject.org"]
subject = "ERROR: fedmsg-migration-tools verify-missing service ({{ env }})"
[log_config.loggers.fedmsg_migration_tools]
level = "INFO"
diff --git a/roles/openshift-apps/messaging-bridges/templates/zmq-to-amqp.toml b/roles/openshift-apps/messaging-bridges/templates/zmq-to-amqp.toml
index fea465585..0205d1ce3 100644
--- a/roles/openshift-apps/messaging-bridges/templates/zmq-to-amqp.toml
+++ b/roles/openshift-apps/messaging-bridges/templates/zmq-to-amqp.toml
@@ -33,7 +33,7 @@ filters = ["ratelimit"]
formatter = "simple"
mailhost = "bastion"
fromaddr = "fedmsg-migration-tools(a)fedoraproject.org"
-toaddrs = ["jcline(a)fedoraproject.org", "abompard(a)fedoraproject.org"]
+toaddrs = ["abompard(a)fedoraproject.org"]
subject = "ERROR: fedmsg-migration-tools zmq-to-amqp bridge"
[log_config.loggers.fedora_messaging]
level = "INFO"
--
2.24.1
4 years, 2 months