Closed
Bug 944131
Opened 11 years ago
Closed 11 years ago
Ensure no private items leak into public cluster
Categories
(Testing :: General, defect)
Tracking
(Not tracked)
RESOLVED
FIXED
People
(Reporter: ekyle, Assigned: ekyle)
References
Details
There is legitimate concern that the public ETL will accidentally leak private bugs/attachments/comments into the public cluster. This bug is to track specific concerns and sanity checks.
:kyle - can you move the prodcut/component to something more aligned for elastic search
Assignee: nobody → klahnakoski
Flags: needinfo?(klahnakoski)
Assignee | ||
Updated•11 years ago
|
Component: Security Assurance → General
Flags: needinfo?(klahnakoski)
Product: mozilla.org → Testing
Version: other → unspecified
Assignee | ||
Comment 2•11 years ago
|
||
The leak_check code (https://github.com/klahnakoski/Bugzilla-ETL/blob/df89c80428ae78fd53b4a05bd94c5949130e6898/tests/resources/python/leak_check.py) is now running every 10min on my staging server, it will email me when a leak is detected.
After a few false start, the latest version of BZ ETL (https://github.com/klahnakoski/Bugzilla-ETL/tree/df89c80428ae78fd53b4a05bd94c5949130e6898) has been running consistently for a day without leaks.
Status: NEW → RESOLVED
Closed: 11 years ago
Resolution: --- → FIXED
Assignee | ||
Comment 3•11 years ago
|
||
Keeping open, for at least one more day
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
Assignee | ||
Comment 4•11 years ago
|
||
Still no leaks. I will reopen if I see anything, but it finally looks good.
Status: REOPENED → RESOLVED
Closed: 11 years ago → 11 years ago
Resolution: --- → FIXED
You need to log in
before you can comment on or make changes to this bug.
Description
•