Closed Bug 1187981 Opened 10 years ago Closed 10 years ago

vct hg-web container broken by bug 1187090

Categories

(Developer Services :: Mercurial: hg.mozilla.org, defect, P1)

Development/Staging
defect

Tracking

(Not tracked)

RESOLVED FIXED

People

(Reporter: smacleod, Assigned: gps)

References

Details

It appears the bug 1187090 broke the test environment (at least for myself). It looks like the hashes listed for packages in the hg-web main.yml task don't match what's being found online. "/var/tmp/epel-release-6-5.noarch.rpm did not match 157da55870a119e39cd2aa3d31e3e340b13b3960b6d5b897a48248c38fe8e1b5; it was 0c42f55f719419fb61caa82fd61ad48b2d32d43bf8c3274197e2506302497b0b." and "var/tmp/ius-release-1.0-14.rpm did not match c2ed9a03f6cbb630a7b4fcdb69a35ddcc4b5d805fbfbd66018996f8df3caa792; it was 331d255903875f47dac8b6acaf299097e70ace2ef55405efc5adb90f1a61158e." Now when attempting to build the docker containers I get the following: > ERROR hgweb> GATHERING FACTS *************************************************************** > ERROR hgweb> ok: [localhost] > ERROR hgweb> > ERROR hgweb> TASK: [hg-web | download IUS community configuration RPMs (RedHat 6)] ********* > ERROR hgweb> skipping: [localhost] => (item={'dest': 'epel-release-6-5.noarch.rpm', 'sha256': '1eac9bf24ae252ae4117a309391b532da3f139e4d0eb8ab384a08f5fc0526593', 'name': 'epel-release-6-5.noarch.rpm'}) > ERROR hgweb> skipping: [localhost] => (item={'dest': 'ius-release-1.0-14.rpm', 'sha256': '147b8d584cff9cb4abc6332999998dc24873fddb0a28b7f505fe993e6331e67c', 'name': 'ius-release-1.0-14.ius.el6.noarch.rpm'}) > ERROR hgweb> > ERROR hgweb> TASK: [hg-web | download IUS community configuration RPMs (CentOS 6)] ********* > ERROR hgweb> failed: [localhost] => (item={'dest': 'epel-release-6-5.noarch.rpm', 'sha256': '157da55870a119e39cd2aa3d31e3e340b13b3960b6d5b897a48248c38fe8e1b5', 'name': 'epel-release-6-5.noarch.rpm'}) => {"failed": true, "item": {"dest": "epel-release-6-5.noarch.rpm", "name": "epel-release-6-5.noarch.rpm", "sha256": "157da55870a119e39cd2aa3d31e3e340b13b3960b6d5b897a48248c38fe8e1b5"}} > ERROR hgweb> msg: The SHA-256 checksum for /var/tmp/epel-release-6-5.noarch.rpm did not match 157da55870a119e39cd2aa3d31e3e340b13b3960b6d5b897a48248c38fe8e1b5; it was 0c42f55f719419fb61caa82fd61ad48b2d32d43bf8c3274197e2506302497b0b. > ERROR hgweb> failed: [localhost] => (item={'dest': 'ius-release-1.0-14.rpm', 'sha256': 'c2ed9a03f6cbb630a7b4fcdb69a35ddcc4b5d805fbfbd66018996f8df3caa792', 'name': 'ius-release-1.0-14.ius.centos6.noarch.rpm'}) => {"failed": true, "item": {"dest": "ius-release-1.0-14.rpm", "name": "ius-release-1.0-14.ius.centos6.noarch.rpm", "sha256": "c2ed9a03f6cbb630a7b4fcdb69a35ddcc4b5d805fbfbd66018996f8df3caa792"}} > ERROR hgweb> msg: The SHA-256 checksum for /var/tmp/ius-release-1.0-14.rpm did not match c2ed9a03f6cbb630a7b4fcdb69a35ddcc4b5d805fbfbd66018996f8df3caa792; it was 331d255903875f47dac8b6acaf299097e70ace2ef55405efc5adb90f1a61158e. > ERROR hgweb> > ERROR hgweb> FATAL: all hosts have already failed -- aborting > ERROR hgweb> > ERROR hgweb> PLAY RECAP ******************************************************************** > ERROR hgweb> to retry, use: --limit @/root/docker-hgweb.retry > ERROR hgweb> > ERROR hgweb> localhost : ok=2 changed=0 unreachable=0 failed=1 > ERROR hgweb>
And I thought these specific packages would be constant over time. Oh well. I'll mirror these in a controlled URL space.
Assignee: nobody → gps
Status: NEW → ASSIGNED
url: https://hg.mozilla.org/hgcustom/version-control-tools/rev/d9bc6f6917952ca2f9741b21d8f6e5a4a57905a6 changeset: d9bc6f6917952ca2f9741b21d8f6e5a4a57905a6 user: Gregory Szorc <gps@mozilla.com> date: Mon Jul 27 10:20:59 2015 -0700 description: ansible/hg-web: self host IUS RPMs (bug 1187981) Upstream packages don't appear to be stable. Host our own mirror that should be stable over time.
Should be fixed now.
Status: ASSIGNED → RESOLVED
Closed: 10 years ago
Resolution: --- → FIXED
hgweb> changed: [localhost] hgweb> hgweb> TASK: [hg-web | set up version-control-tools repo] **************************** hgweb> failed: [localhost] => {"failed": true} hgweb> msg: abort: unknown revision '28d896bdd040'! hgweb> hgweb> hgweb> FATAL: all hosts have already failed -- aborting hgweb> hgweb> PLAY RECAP ******************************************************************** hgweb> to retry, use: --limit @/root/docker-hgweb.retry hgweb> hgweb> localhost : ok=21 changed=19 unreachable=0 failed=1 hgweb> ERROR hgweb> changed: [localhost] ERROR hgweb> ERROR hgweb> TASK: [hg-web | copy requirements.txt] **************************************** ERROR hgweb> changed: [localhost] ERROR hgweb> ERROR hgweb> TASK: [hg-web | populate hgweb virtualenv] ************************************ ERROR hgweb> changed: [localhost] ERROR hgweb> ERROR hgweb> TASK: [hg-web | set up version-control-tools repo] **************************** ERROR hgweb> failed: [localhost] => {"failed": true} ERROR hgweb> msg: abort: unknown revision '28d896bdd040'! ERROR hgweb> ERROR hgweb> ERROR hgweb> FATAL: all hosts have already failed -- aborting ERROR hgweb> ERROR hgweb> PLAY RECAP ******************************************************************** ERROR hgweb> to retry, use: --limit @/root/docker-hgweb.retry ERROR hgweb> ERROR hgweb> localhost : ok=21 changed=19 unreachable=0 failed=1 ERROR hgweb>
Status: RESOLVED → REOPENED
Resolution: FIXED → ---
I can reproduce this failure. Will fix.
url: https://hg.mozilla.org/hgcustom/version-control-tools/rev/1e79b0994d9338c524a2b1c6a94eb2d0eb481a10 changeset: 1e79b0994d9338c524a2b1c6a94eb2d0eb481a10 user: Gregory Szorc <gps@mozilla.com> date: Mon Jul 27 12:52:35 2015 -0700 description: ansible/hg-web: use local v-c-t repo when running in Docker (bug 1187981) Previously, hg-web would always `hg clone` version-control-tools from hg.mozilla.org. When running locally inside Docker against a changeset that hadn't been pushed yet, this would fail because the changeset wasn't on hg.mozilla.org. We conditionalize the v-c-t repo interaction behavior to facilitate working within Docker. If the /vct directory is available (which it will be for all Ansible-based Docker images), we rsync v-c-t from there instead of attempting to clone it. We won't have a .hg directory in /repo/hg/version-control-tools. But, that shouldn't matter since we shouldn't be doing any repository interaction on that repo during normal operations.
I think I got it this time.
Status: REOPENED → RESOLVED
Closed: 10 years ago10 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.