Closed Bug 1557885 Opened 7 years ago Closed 7 years ago

Intermittent ModuleNotFoundError: No module named 'mozpack'

Categories

(Release Engineering :: Release Automation, defect, P5)

defect

Tracking

(firefox-esr60 fixed, firefox67 fixed, firefox68 fixed, firefox69 fixed)

RESOLVED FIXED
Tracking Status
firefox-esr60 --- fixed
firefox67 --- fixed
firefox68 --- fixed
firefox69 --- fixed

People

(Reporter: intermittent-bug-filer, Unassigned)

References

(Regression)

Details

(Keywords: intermittent-failure, regression)

Filed by: apavel [at] mozilla.com
Parsed log: https://treeherder.mozilla.org/logviewer.html#?job_id=250719262&repo=mozilla-central
Full log: https://queue.taskcluster.net/v1/task/fb3r3LckStuGE2qwriR-xA/runs/0/artifacts/public/logs/live_backing.log


Traceback (most recent call last):
File "/builds/scriptworker/bin/signingscript", line 7, in <module>
from signingscript.script import main
File "/builds/scriptworker/lib/python3.6/site-packages/signingscript/script.py", line 11, in <module>
from signingscript.task import build_filelist_dict, get_token,
File "/builds/scriptworker/lib/python3.6/site-packages/signingscript/task.py", line 24, in <module>
from signingscript.sign import get_suitable_signing_servers, sign_gpg,
File "/builds/scriptworker/lib/python3.6/site-packages/signingscript/sign.py", line 57, in <module>
from mozpack import mozjar # noqa: E402
ModuleNotFoundError: No module named 'mozpack'
exit code: 1

Flags: needinfo?(bugspam.Callek)

This was caused by https://github.com/mozilla-releng/build-puppet/pull/506 actually the PR for 507 was the fix.

The underlying change was that in signingscript with https://github.com/mozilla-releng/signingscript/pull/106 and related https://github.com/mozilla-releng/signingscript/pull/111

Initial testing happened on one single instance, which I was using pip install -e . for signingscript and not an install via wheel. So travis and the scriptworker instance both succeeded. However once installed via wheel the production instance failed.

There are two possible ways to fix this better, and we'll approach them next week (sometime monday to start) at which point we'll make sure to test the deployment same as it would be tested in production.

Status: NEW → RESOLVED
Closed: 7 years ago
Flags: needinfo?(bugspam.Callek)
Regressed by: 1533818
Resolution: --- → FIXED
Component: Release Automation: Signing → Release Automation
You need to log in before you can comment on or make changes to this bug.