Closed Bug 1459752 Opened 7 years ago Closed 7 years ago

Bugzilla-ETL appears to be failing

Categories

(bugzilla.mozilla.org :: Infrastructure, defect)

Product:
bugzilla.mozilla.org
Component:
Infrastructure
Version:
Production
Type:
defect
Priority:
Not set
Severity:
normal

Tracking

()

Status:
RESOLVED FIXED

People

(Reporter: ekyle, Unassigned)

References

Details

The public cluster has stale data. The ETL may have stopped! The last good date was May4th, in the ?morning? (timezones make it too difficult to know for sure).
This because it can't connect to db-bugs-ro. NI on cvalaas to see if there's anything left of the BMO DB in SCL3; otherwise, what's the stats of the migration of this to AWS?
Flags: needinfo?(klahnakoski)
Flags: needinfo?(cvalaas)
MOC has shutdown the bugzilla db servers (#1459316) but they haven't been receiving updates from the new master in AWS since May 4. We could turn them back on but they'd still be only stale data. You should be able to point to the database in AWS for the latest info, :bobm and :ckolos can set up the perms for that, I believe.
Flags: needinfo?(cvalaas)
Had a vidyo chat w/ bobm and ckolos and they're going to get me creds for RDS, as well as setting up a path for etl to connect to them. And I believe that they and ekyle (and hopefully me) are getting together on Thurs to talk about the overall plan to migrate...
Flags: needinfo?(klahnakoski)
(In reply to Kendall Libby [:fubar] from comment #3) > they're going to get me creds for RDS credentials and db host ip have been updated in puppet. just need network access now.
appears to be working
Status: NEW → RESOLVED
Closed: 7 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.