Blockerbugs generates regular emails with problems looking for f30 which doesn't exist.
Cron blockerbugs@blockerbugs01 blockerbugs sync Inbox x A-Fed-IS-Stuff/Cleanup x  (Cron Daemon) blockerbugs@fedoraproject.org 12:00 (7 minutes ago)  to sysadmin-qa-members  /usr/lib/python2.7/site-packages/flask_sqlalchemy/init.py:794: FSADeprecationWarning: SQLALCHEMY_TRACK_MODIFICATIONS adds significant overhead and will be disabled by default in the future. Set it to True or False to suppress this warning. 'SQLALCHEMY_TRACK_MODIFICATIONS adds significant overhead and ' connectionpool 2019-02-28 17:00:03 INFO Starting new HTTPS connection (1): bugzilla.redhat.com bz_interface 2019-02-28 17:00:03 INFO Using bugzilla URL: https://bugzilla.redhat.com/xmlrpc.cgi bug_sync 2019-02-28 17:00:03 INFO Starting blocker sync bug_sync 2019-02-28 17:00:03 INFO Syncing blockers for milestone milestone: 30-beta bug_sync 2019-02-28 17:00:03 INFO Cleaning up Blocker for Fedora 30 beta (1574713) connectionpool 2019-02-28 17:00:03 INFO Resetting dropped connection: bugzilla.redhat.com bug_sync 2019-02-28 17:00:03 INFO Updating Blocker for Fedora 30 beta (1574713) connectionpool 2019-02-28 17:00:03 INFO Resetting dropped connection: bugzilla.redhat.com bug_sync 2019-02-28 17:00:04 INFO Syncing FE for milestone milestone: 30-beta bug_sync 2019-02-28 17:00:04 INFO Cleaning up FreezeException for Fedora 30 beta (1574714) connectionpool 2019-02-28 17:00:04 INFO Resetting dropped connection: bugzilla.redhat.com bug_sync 2019-02-28 17:00:05 INFO Updating FreezeException for Fedora 30 beta (1574714) connectionpool 2019-02-28 17:00:05 INFO Resetting dropped connection: bugzilla.redhat.com bug_sync 2019-02-28 17:00:05 INFO Syncing PrioritizedBug for milestone milestone: 30-beta bug_sync 2019-02-28 17:00:05 INFO Cleaning up PrioritizedBug for Fedora 30 beta bug_sync 2019-02-28 17:00:05 INFO Updating PrioritizedBug for Fedora 30 beta connectionpool 2019-02-28 17:00:05 INFO Resetting dropped connection: bugzilla.redhat.com bug_sync 2019-02-28 17:00:06 INFO Syncing blockers for milestone milestone: 30-final bug_sync 2019-02-28 17:00:06 INFO Cleaning up Blocker for Fedora 30 final (1574715) connectionpool 2019-02-28 17:00:06 INFO Resetting dropped connection: bugzilla.redhat.com bug_sync 2019-02-28 17:00:07 INFO Updating Blocker for Fedora 30 final (1574715) connectionpool 2019-02-28 17:00:07 INFO Resetting dropped connection: bugzilla.redhat.com bug_sync 2019-02-28 17:00:07 INFO Syncing FE for milestone milestone: 30-final bug_sync 2019-02-28 17:00:07 INFO Cleaning up FreezeException for Fedora 30 final (1574716) connectionpool 2019-02-28 17:00:07 INFO Resetting dropped connection: bugzilla.redhat.com bug_sync 2019-02-28 17:00:07 INFO Updating FreezeException for Fedora 30 final (1574716) connectionpool 2019-02-28 17:00:07 INFO Resetting dropped connection: bugzilla.redhat.com bug_sync 2019-02-28 17:00:08 INFO Syncing PrioritizedBug for milestone milestone: 30-final bug_sync 2019-02-28 17:00:08 INFO Cleaning up PrioritizedBug for Fedora 30 final bug_sync 2019-02-28 17:00:08 INFO Updating PrioritizedBug for Fedora 30 final connectionpool 2019-02-28 17:00:08 INFO Resetting dropped connection: bugzilla.redhat.com update_sync 2019-02-28 17:00:09 INFO found 57 bugs in f29 release connectionpool 2019-02-28 17:00:09 INFO Starting new HTTPS connection (1): bodhi.fedoraproject.org update_sync 2019-02-28 17:00:27 INFO found 20 updates from bodhi for 57 bugs in f29 update_sync 2019-02-28 17:00:27 INFO found 19 bugs in f30 release update_sync 2019-02-28 17:00:27 ERROR Invalid releases specified: f30 Traceback (most recent call last): File "/usr/lib/python2.7/site-packages/blockerbugs/util/update_sync.py", line 122, in search_updates result = self.bodhi_interface.query(**queries_data) File "/usr/lib/python2.7/site-packages/fedora/client/bodhi.py", line 118, in wrapper raise BodhiClientException(problems) BodhiClientException: Invalid releases specified: f30
When do you need this? (YYYY/MM/DD)
When is this no longer needed or useful? (YYYY/MM/DD)
If we cannot complete your request, what is the impact?
CC @tflink
Metadata Update from @bowlofeggs: - Issue priority set to: Waiting on Assignee (was: Needs Review)
The error here was fixed in ansible commit c39397d028c2c729ad6728dec31c427451ff9fc6
The cron emails are still produced. I think @tflink wanted to keep getting them for some reason? Personally, I'd prefer it send emails only for errors and just log the information in the normal emails if possible, but thats another issue I guess.
Metadata Update from @kevin: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)