Closed Bug 1717534 Opened 4 years ago Closed 4 years ago

Support treestatus groups for esr91

Categories

(Release Engineering :: General, task)

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: jmaher, Assigned: jmaher)

References

Details

prior art in Bug 1645646 (for esr78)

Assignee: nobody → jmaher

landed code, also landed on staging ( https://stage.treestatus.mozilla-releng.net/static/ui/treestatus/ ):
https://github.com/mozilla-releng/treestatus/commits/staging

but staging failed to deploy according to:
https://ops-master.jenkinsv2.prod.mozaws.net/job/gcp-pipelines/job/relengapi/job/treestatus-staging/67/

I am not too familiar with all of this- if I don't figure it out today, it might have to wait a few weeks while I am on PTO or wait until someone else picks this up.

Digging into Jenkins, I see:

2021-06-25 20:14:45,716 INFO     Validating: mozilla/releng-treestatus:staging Digest: sha256:629840b1b48f7b8ee7c101e864c43905f503bbfbdd5bc204073eca77bb426ab1 Build URL: https://firefox-ci-tc.services.mozilla.com/tasks/K9WVXWqbSbiKXiG-4RJ2tw
2021-06-25 20:14:45,716 INFO     Validating against TaskCluster
2021-06-25 20:14:45,868 INFO     Running: docker rmi mozilla/releng-treestatus:staging
2021-06-25 20:14:46,735 INFO     Running: docker logout
Traceback (most recent call last):
  File "/home/jenkins/slave/workspace/gcp-pipelines/relengapi/treestatus-staging/./projects/relengapi/treestatus", line 11, in <module>
    cli.group()
  File "/usr/local/lib/python3.9/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/local/lib/python3.9/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/local/lib/python3.9/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/usr/local/lib/python3.9/site-packages/deploylib/cli.py", line 208, in mirror_image
    docker.mirror_image(src, dest, validate, version_location)
  File "/usr/local/lib/python3.9/site-packages/deploylib/docker.py", line 254, in mirror_image
    validate_image(
  File "/usr/local/lib/python3.9/site-packages/deploylib/docker.py", line 235, in validate_image
    return validate_digest_taskcluster(image_build_url, image_digest)
  File "/usr/local/lib/python3.9/site-packages/deploylib/docker.py", line 222, in validate_digest_taskcluster
    raise Exception(f"Digest: {image_digest} not found in {build_url}")
Exception: Digest: sha256:629840b1b48f7b8ee7c101e864c43905f503bbfbdd5bc204073eca77bb426ab1 not found in https://firefox-ci-tc.services.mozilla.com/tasks/K9WVXWqbSbiKXiG-4RJ2tw

But the task seems green and push skipped since image already exists. I wonder when did we last have a successful push to staging? I don't think we've touched this repo in a good while.

Speaking of which, I can't find docs on how to push this to staging.
@ben - do you have any idea of what's going on here?

Flags: needinfo?(bhearsum)

(In reply to Mihai Tabara [:mtabara]⌚️GMT from comment #3)

raise Exception(f"Digest: {image_digest} not found in {build_url}")

Exception: Digest: sha256:629840b1b48f7b8ee7c101e864c43905f503bbfbdd5bc204073eca77bb426ab1 not found in https://firefox-ci-tc.services.mozilla.com/tasks/K9WVXWqbSbiKXiG-4RJ2tw

Speaking of which, I can't find docs on how to push this to staging.
@ben - do you have any idea of what's going on here?

This is an error during CloudOps' verification that the image they downloaded matches the one that was built by looking at the Taskcluster log. I'm not seeing any obvious reason why it fails -- the sha noted aboved is presented in the task log that jenkins should be looking at (https://firefoxci.taskcluster-artifacts.net/K9WVXWqbSbiKXiG-4RJ2tw/0/public/logs/live_backing.log).

I tried it again, and this time it worked. It was probably some random network failure that broke it -- the jenkins/deploylib logs don't log enough to really know for sure.

Flags: needinfo?(bhearsum)

Merged master -> production to be up to date. All good.

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