Properties
Properties
Drydock: Run Command on atomic02.kolabsys.com
Drydock: Run Command on atomic02.kolabsys.com
- When
- Completed at Mar 7 2016, 6:14 AM · Built for 8 m, 45 s
- Status
Failed
| 38 | + git reset --hard origin/master |
|---|---|
| 39 | + git clean -d -f -x |
| 40 | + popd |
| 41 | + export commit |
| 42 | + export differential |
| 43 | + export id |
| 44 | + export package |
| 45 | + export phid |
| 46 | + export ro_uri |
| 47 | + export uri |
| 48 | + export vcs |
| 49 | + export test_build |
| 50 | + export test_functional |
| 51 | + export test_integration |
| 52 | + export test_performance |
| 53 | + export test_unit |
| 54 | + export test_obs |
| 55 | + '[' '!' -d /var/tmp/osbuild-packagecache ']' |
| 56 | + '[' -x stick.git/drydocker/docker/build.sh ']' |
| 57 | + pushd docker.git |
| 58 | + ../stick.git/drydocker/docker/build.sh |
| 59 | /bin/sh: line 2: kubectl: command not found |
| 60 | /bin/sh: line 2: kubectl: command not found |
| 61 | /bin/sh: line 2: kubectl: command not found |
| 62 | Error response from daemon: Cannot destroy container 84c439d65176: Conflict, You cannot remove a running container. Stop the container before attempting removal or use -f |
| 63 | Error: failed to remove containers: [84c439d65176] |
| 64 | Error response from daemon: Cannot destroy container b49f126c8f8b: Failed to set container state to RemovalInProgress: Status is already RemovalInProgress |
| 65 | Error: failed to remove containers: [b49f126c8f8b] |
| 66 | Error response from daemon: Cannot destroy container cfad6c5aebee: Failed to set container state to RemovalInProgress: Status is already RemovalInProgress |
| 67 | Error: failed to remove containers: [cfad6c5aebee] |
| 68 | Error response from daemon: Cannot destroy container 51d55b623674: Failed to set container state to RemovalInProgress: Status is already RemovalInProgress |
| 69 | Error: failed to remove containers: [51d55b623674] |
| 70 | Error response from daemon: Cannot destroy container 4d2f0d21dfe7: Failed to set container state to RemovalInProgress: Status is already RemovalInProgress |
| 71 | Error: failed to remove containers: [4d2f0d21dfe7] |
| 72 | Error response from daemon: Conflict, cannot delete because dc772df7317b is held by an ongoing pull or build |
| 73 | Error: failed to remove images: [dc772df7317b] |
| 74 | ../stick.git/drydocker/docker/build.sh: line 19: pushd: /srv/.git: No such file or directory |
| 75 | ../stick.git/drydocker/docker/build.sh: line 25: popd: directory stack empty |
| 76 | The command '/bin/sh -c yum clean all && yum -y install epel-release && rpm --import /etc/pki/rpm-gpg/RPM-GPG-KEY-EPEL-7 && sed -i -e 's/#baseurl/baseurl/g' -e '/^mirrorlist/d' /etc/yum.repos.d/epel*.repo && yum -y install yum-plugin-priorities && yum -y update && yum -y install @buildsys-build ant bind-utils build git lsof net-tools nmap-ncat openldap-clients osc perl-Data-Dumper perl-Digest-MD5 perl-TimeDate php-phpunit-PHPUnit-Selenium policycoreutils policycoreutils-python psmisc rpmdevtools screen strace sudo telnet traceroute vim-enhanced wget yum-utils && yum clean all' returned a non-zero code: 1 |
| 77 | make: *** [ci-maipo] Error 1 |
| 78 | Error response from daemon: Conflict, cannot delete because 949a398daf4b is held by an ongoing pull or build |
| 79 | Error: failed to remove images: [949a398daf4b] |
| 80 | Error response from daemon: Conflict, cannot delete 297df435b4b1 because the container 03798bb2f469 is using it, use -f to force |
| 81 | Error: failed to remove images: [297df435b4b1] |
| 82 | Error response from daemon: Conflict, cannot delete because e51aa6dbf2dd is held by an ongoing pull or build |
| 83 | Error: failed to remove images: [e51aa6dbf2dd] |
| 84 | + retval=2 |
| 85 | + popd |
| 86 | + exit 2 |
| 87 |
| 297 | [91mhttp://download.fedoraproject.org/pub/epel/7/x86_64/repodata/d4952e10826f5fc4918df96721108fe7458dfb3bbe16da96fdf853c255cbef75-updateinfo.xml.bz2: [Errno 14] HTTP Error 404 - Not Found |
|---|---|
| 298 | Trying other mirror. |
| 299 | To address this issue please refer to the below knowledge base article |
| 300 | |
| 301 | https://access.redhat.com/articles/1320623 |
| 302 | |
| 303 | If above article doesn't help to resolve this issue please create a bug on https://bugs.centos.org/ |
| 304 | |
| 305 | [0m[91mhttp://download.fedoraproject.org/pub/epel/7/x86_64/repodata/ea6d135f6b0626e69a0def6eccf5eea135c355765dd607e9c0bc6e1a2d6c8c2e-primary.sqlite.xz: [Errno 14] HTTP Error 404 - Not Found |
| 306 | [0m[91mTrying other mirror. |
| 307 | [0m[91mhttp://download.fedoraproject.org/pub/epel/7/x86_64/repodata/ea6d135f6b0626e69a0def6eccf5eea135c355765dd607e9c0bc6e1a2d6c8c2e-primary.sqlite.xz: [Errno 14] HTTP Error 404 - Not Found |
| 308 | Trying other mirror. |
| 309 | [0m[91mhttp://download.fedoraproject.org/pub/epel/7/x86_64/repodata/ea6d135f6b0626e69a0def6eccf5eea135c355765dd607e9c0bc6e1a2d6c8c2e-primary.sqlite.xz: [Errno 14] HTTP Error 404 - Not Found |
| 310 | Trying other mirror. |
| 311 | [0m[91m |
| 312 | |
| 313 | One of the configured repositories failed (Extra Packages for Enterprise Linux 7 - x86_64), |
| 314 | and yum doesn't have enough cached data to continue. At this point the only |
| 315 | safe thing yum can do is fail. There are a few ways to work "fix" this: |
| 316 | |
| 317 | 1. Contact the upstream for the repository and get them to fix the problem. |
| 318 | |
| 319 | 2. Reconfigure the baseurl/etc. for the repository, to point to a working |
| 320 | upstream. This is most often useful if you are using a newer |
| 321 | distribution release than is supported by the repository (and the |
| 322 | packages for the previous distribution release still work). |
| 323 | |
| 324 | 3. Disable the repository, so yum won't use it by default. Yum will then |
| 325 | just ignore the repository until you permanently enable it again or use |
| 326 | --enablerepo for temporary usage: |
| 327 | |
| 328 | yum-config-manager --disable epel |
| 329 | |
| 330 | 4. Configure the failing repository to be skipped, if it is unavailable. |
| 331 | Note that yum will try to contact the repo. when it runs most commands, |
| 332 | so will have to try and fail each time (and thus. yum will be be much |
| 333 | slower). If it is a very temporary problem though, this is often a nice |
| 334 | compromise: |
| 335 | |
| 336 | yum-config-manager --save --setopt=epel.skip_if_unavailable=true |
| 337 | |
| 338 | failure: repodata/ea6d135f6b0626e69a0def6eccf5eea135c355765dd607e9c0bc6e1a2d6c8c2e-primary.sqlite.xz from epel: [Errno 256] No more mirrors to try. |
| 339 | http://download.fedoraproject.org/pub/epel/7/x86_64/repodata/ea6d135f6b0626e69a0def6eccf5eea135c355765dd607e9c0bc6e1a2d6c8c2e-primary.sqlite.xz: [Errno 14] HTTP Error 404 - Not Found |
| 340 | [0mDeleted: e0745dc9eff701e73af1315f101d68505da89368065873d8b54b3dd2684a1a6a |
| 341 | Deleted: 10c49d66ec7ccde7f749a7eb2490030c75f55c8d7b9a92779725665af57cbd09 |
| 342 | Deleted: 283254fa75313b725aa73e7f98d539be1245e8b4797521b4075d3c85fca1b442 |
| 343 | Deleted: f682b738ddaec9bae68e7cae2f2285bb24db93e5d72b5795b81e1c9c610e39f2 |
| 344 | Deleted: 460dd918d03086f1b9e75ec8c269d0c6eafcd8fd81cc74dca1ca940f715abf6a |
| 345 | /var/drydock/workingcopy-60/repo/docker |
| 346 |
Lease Working Copy on atomic02.kolabsys.com
Lease Working Copy on atomic02.kolabsys.com
- When
- Completed at Mar 7 2016, 6:05 AM · Built instantly
- Status
Passed