Trees closed due to "Error: Cannot retrieve repository metadata (repomd.xml) for repository: centos6. Please verify its path and try again"

RESOLVED FIXED

Status

Release Engineering
Buildduty
--
blocker
RESOLVED FIXED
4 years ago
4 years ago

People

(Reporter: emorley, Unassigned)

Tracking

Firefox Tracking Flags

(Not tracked)

Details

(Reporter)

Description

4 years ago
Just started happening on multiple repos:

https://tbpl.mozilla.org/php/getParsedLog.php?id=40964391&tree=B2g-Inbound
https://tbpl.mozilla.org/php/getParsedLog.php?id=40964590&tree=B2g-Inbound
https://tbpl.mozilla.org/php/getParsedLog.php?id=40964577&tree=Mozilla-B2g30-v1.4

{
State Changed: running yum
ERROR: Command failed: 
 # ['/usr/bin/yum', '--installroot', '/builds/mock_mozilla/mozilla-centos6-i386/root/', 'install', 'bash', 'bzip2', 'coreutils', 'cpio', 'diffutils', 'fedora-release', 'findutils', 'gawk', 'gmp', 'libstdc++', 'ppl', 'cpp', 'gcc', 'gcc-c++', 'grep', 'gzip', 'info', 'make', 'patch', 'redhat-rpm-config', 'rpm-build', 'sed', 'shadow-utils', 'tar', 'unzip', 'util-linux', 'which', 'xz']
http://repos/repos/yum/mirrors/centos/6/latest/os/i386/repodata/repomd.xml: [Errno 14] PYCURL ERROR 22 - "The requested URL returned error: 404"
Trying other mirror.
Error: Cannot retrieve repository metadata (repomd.xml) for repository: centos6. Please verify its path and try again

program finished with exit code 30
elapsedTime=1.117693
========= Finished mock-tgt mozilla-centos6-i386 failed (results: 2, elapsed: 1 secs) (at 2014-06-03 09:04:01.008738) =========
}

All trees closed.
That 'repos' CNAME pointed to a puppetmaster that deleted its repos due to rsync'ing from the distinguished master while /data/ was unmounted and thus empty.  I've pointed 'repos' elsewhere, turned off httpd on that host, and begun re-syncing it (which needed to happen anyway per bug 999661), so this should be clear now.  Ryan's re-triggered and we're waiting to hear.
Depends on: 899548
Depends on: 999661
Haven't seen any for awhile now. Trees reopened.
Status: NEW → RESOLVED
Last Resolved: 4 years ago
Resolution: --- → FIXED
You need to log in before you can comment on or make changes to this bug.