The list of opened bugs should look like this:

https://bugzilla.redhat.com/buglist.cgi?bug_status=NEW&bug_status=ASSIGNED&bug_status=POST&bug_status=MODIFIED&bug_status=ON_DEV&bug_status=ON_QA&bug_status=VERIFIED&bug_status=RELEASE_PENDING&f1=blocked&f2=status_whiteboard&list_id=1792056&o1=substring&o2=substring&order=component%2Cbug_id&query_based_on=&query_format=advanced&v1=980651&v2=AcceptedBlocker

Thanks for the reminder. I tried looking at it yesterday when I first noticed but couldn't get into the production machines and promptly forgot about it.

https://fedorahosted.org/fedora-infrastructure/ticket/4060

Either martin or I will look into this as soon as we can get logs or if we can get this reproduced locally

I think I figured this out, and it's not as bad as I was thinking at first.

When we query bugzilla, we're limiting the status to:
{{{
BUG_STATUS = ['NEW', 'ASSIGNED', 'ON_DEV', 'MODIFIED', 'POST', 'ON_QA', 'FAILS_QA','PASSES_QA', 'REOPENED', 'VERIFIED', 'RELEASE_PENDING']
}}}

This excludes CLOSED bugs from being picked up and updated in the database. When I remove this restriction, the sync updates closed bugs as expected.

I don't know why this became an issue all of a sudden (this was carried over from the old wiki updating script that jlaska wrote) but I'll get a fix ready for testing on staging ... assuming I can get access to stg for testing, anyways.

Fix posted to t421-closedsyncfailure branch:

https://git.fedorahosted.org/cgit/blockerbugs.git/commit/?h=hotfix/t421-closedsyncfailure&id=e37129e7a5c119d43ac296a09d0f7ff9e8d42795

Review up:
https://reviewboard-tflink.rhcloud.com/r/53/

It's working on my local machine against partner-bugzilla. I'll try deploying to staging, assuming I can get access to it.

Code reviewed by mkrizek (despite my botched diff). merged and pushed to origin.
master: e37129e7a5c119d43ac296a09d0f7ff9e8d42795
develop: 0383287a5fa3e04df5d5db1c5d4229903a63dd3c

I will be getting a new version into stg soon, will close this ticket once it has been deployed to production.

Apologies on the delay but the fix has now been deployed to production. It appears as if bugs are being removed from the list as they are closed, so I'm closing the ticket.

Please re-open if this turns out not to be the case