Closed Bug 1580539 Opened 6 years ago Closed 6 years ago

Latest iodide not deploying

Categories

(Cloud Services :: Iodide, task, P1)

Product:
Cloud Services
Component:
Iodide
Type:
task

Tracking

(Not tracked)

Status:
RESOLVED FIXED

People

(Reporter: wlach, Assigned: robotblake)

References

Details

Something about the new docker images we started creating after #2163 is not passing deploy. See this in the #iodide-deploys slack channel:

Start building data/iodide latest stage/prod pipeline, build #847
iodide[324] GCP STAGE STARTED
cloudops-jenkinsAPP 10:27 AM
iodide[324] GCP STAGE FAILED @robotblake
data/iodide build #846: hub.prod.mozaws.net/pipelines/data-iodide:latest-846 deployed to stage.
data/iodide build #847: hub.prod.mozaws.net/pipelines/data-iodide:latest-847 deployed to stage.

I don't think I have access to the jenkins instance that is performing these operations. Blake, could you copy paste whatever you're seeing there? This problem should be very easy to solve once we know what's going on -- probably just a one liner fix to the docker image.

Flags: needinfo?(bimsland)

So this is down to the built images not containing the python libraries from the requirements file, I'm going to work on a PR to fix the issues and get that up for review.

Flags: needinfo?(bimsland)
Assignee: wlachance → bimsland
Priority: -- → P1

This was fixed with this commit.

Status: NEW → RESOLVED
Closed: 6 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.