My custom reports reported errors for data from yesterday (2015-01-13) when running today, I guess it's out of sync with the main instance of Postgres. This is critical as it hinders me from most of my stability reporting to release management and breaks all reports I produce, including arewestableyet.com
mpressman, could this be related to the r/w master switchover last night?
Yep, it is related. The new server to use is socorro-reporting2.db.phx1.mozilla.com This replaces the older socorro-reporting1.db.phx1.mozilla.com and is up to date with the new master
OK, with bug 1121697 resolved, this seems to work now, thanks for looking into this!
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.