Bug 1396689

Summary:	Bodhi sending too many e-mail
Product:	[Fedora] Fedora	Reporter:	Bojan Smojver <bojan>
Component:	bodhi	Assignee:	Randy Barlow <randy>
Status:	CLOSED ERRATA	QA Contact:	Fedora Extras Quality Assurance <extras-qa>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	rawhide	CC:	lewk, randy
Target Milestone:	---	Keywords:	Reopened
Target Release:	---
Hardware:	All
OS:	Linux
Whiteboard:
Fixed In Version:	bodhi-2.3.3-4.el7	Doc Type:	If docs needed, set a value
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-02-25 02:49:46 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Bojan Smojver 2016-11-19 00:35:47 UTC

Description of problem:
Check out this, for instance:

https://bodhi.fedoraproject.org/updates/FEDORA-2016-f5e78ec298

I got like a 100 e-mails about the release being ready to be pushed to stable. Can we have that reduced to one or maybe just e-mail the person that owns the update instead of anyone that commented?

Version-Release number of selected component (if applicable):
bodhi-2.3.1

How reproducible:
Always.

Steps to Reproduce:
1. Be unlucky and comment on one such update.
2. Receive spam. :-(

Actual results:
Spam.

Expected results:
More quiet operation.

Additional info:

Comment 1 Randy Barlow 2016-11-19 22:50:35 UTC

Hello Bojan! I apologize for the e-mails. It was an issue that I thought I had fixed with 2.3.0, but apparently there is still some case that causes it to happen. There's an upstream ticket for this issue that I reopened this week, so I'm closing this and linking it there. Thanks for you patience as we work to solve it!

Comment 2 Bojan Smojver 2016-11-20 01:18:41 UTC

Thank you!

Comment 3 Bojan Smojver 2017-02-06 00:35:47 UTC

This issue appears to be back. See https://bodhi.fedoraproject.org/updates/FEDORA-2017-472052ebe5 for an example.

Comment 4 Randy Barlow 2017-02-06 13:45:59 UTC

Ah, the joys of hotfixing. This issue was never fixed in an RPM, but was unfortunately only hotfixed in production with the idea that we'd make a new upstream release soon enough that contains the fix. Unfortunately, we've not made an upstream release in a while. Last week we deployed a new RPM that had other patches we wanted to apply to production and we had forgotten to include these patches in that RPM.

I will make a new RPM with these patches.

Comment 5 Fedora Update System 2017-02-06 14:41:40 UTC

bodhi-2.3.3-4.el7 python-fedmsg-atomic-composer-2016.3-1.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-cd060eeb3c

Comment 6 Fedora Update System 2017-02-06 14:41:47 UTC

bodhi-2.3.3-4.el7 python-fedmsg-atomic-composer-2016.3-1.el7 has been submitted as an update to Fedora EPEL 7. https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-cd060eeb3c

Comment 7 Randy Barlow 2017-02-06 15:04:25 UTC

bodhi-2.3.3-4.el7 and bodhi-2.3.3-5.fc25 have been installed on production and this issue should stay fixed now.

Comment 8 Fedora Update System 2017-02-07 04:17:54 UTC

bodhi-2.3.3-4.el7, python-fedmsg-atomic-composer-2016.3-1.el7 has been pushed to the Fedora EPEL 7 testing repository. If problems still persist, please make note of it in this bug report.
See https://fedoraproject.org/wiki/QA:Updates_Testing for
instructions on how to install test updates.
You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2016-cd060eeb3c

Comment 9 Fedora Update System 2017-02-25 02:49:46 UTC

bodhi-2.3.3-4.el7, python-fedmsg-atomic-composer-2016.3-1.el7 has been pushed to the Fedora EPEL 7 stable repository. If problems still persist, please make note of it in this bug report.