Closed Bug 1337995 Opened 9 years ago Closed 9 years ago

Pin or otherwise resolve python_moztelemetry protobuf dependency

Categories

(Cloud Services Graveyard :: Metrics: Pipeline, defect, P2)

defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: whd, Assigned: mdoglio)

References

Details

Attachments

(1 file)

At some point today a new release of on pypi for the protobuf dependency occurred that broke our python spark clusters, including scheduled jobs: https://pypi.python.org/pypi/protobuf/3.2.0 I manually patched the requirements in the bootstrap script to load 3.1.0, which works, because I off-hand do not know how to reference the appropriate version of 3.2.0 (the one uploaded on 2017-01-30, as opposed to the newer protobuf-3.2.0-cp27-cp27mu-manylinux1_x86_64.whl). We should either permanently pin protobuf to a working version or otherwise resolve this.
Points: --- → 1
Priority: -- → P2
The temporary fix was made "permanent" by https://github.com/mozilla/emr-bootstrap-spark/pull/62 but we should still figure out what the right thing to do here is.
Pinning protobuf seems the right thing to do short term. I'll open a pull request for python_moztelemetry.
Assignee: nobody → mdoglio
Status: NEW → RESOLVED
Closed: 9 years ago
Resolution: --- → FIXED
Product: Cloud Services → Cloud Services Graveyard
You need to log in before you can comment on or make changes to this bug.

Attachment

General

Created:
Updated:
Size: