CENGN build container failure on golang
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
StarlingX |
Fix Released
|
High
|
Scott Little |
Bug Description
Brief Description
-----------------
Intermittent build failure seen by CENGN when constructing the build container.
Failed to yum install golang.
Error is 404 on ftp.iij.
Why are we even looking for this repo at this stage?
Severity
--------
Major
Steps to Reproduce
------------------
docker build --build-arg MYUID=18876 --build-arg MYUNAME=jenkins --ulimit core=0 --network host --tag jenkins:
Expected Behavior
------------------
Successful creation of a docker image in which to run the build
Actual Behavior
----------------
Failed to construct a docker image in which to run the build
Reproducibility
---------------
Intermittent. 15%
System Configuration
-------
N/A
Branch/Pull Time/Commit
-------
20190619T013000Z
Last Pass
---------
20190617T233000Z
Timestamp/Logs
--------------
...
Step 36/37 : RUN yum install -y golang; mkdir -p ${GOPATH}/bin; curl https:/
---> Running in fe6ae2f54414
Loaded plugins: fastestmirror, ovl
http://
Trying other mirror.
To address this issue please refer to the below knowledge base article
https:/
If above article doesn't help to resolve this issue please create a bug on https:/
Loading mirror speeds from cached hostfile
* base: centos.
* extras: centos.
* updates: centos.
http://
Trying other mirror.
http://
Trying other mirror.
One of the configured repositories failed (Starlingx-
and yum doesn't have enough cached data to continue. At this point the only
safe thing yum can do is fail. There are a few ways to work "fix" this:
1. Contact the upstream for the repository and get them to fix the problem.
2. Reconfigure the baseurl/etc. for the repository, to point to a working
upstream. This is most often useful if you are using a newer
distribution release than is supported by the repository (and the
packages for the previous distribution release still work).
3. Run the command with the repository temporarily disabled
yum --disablerepo=
4. Disable the repository permanently, so yum won't use it by default. Yum
will then just ignore the repository until you permanently enable it
again or use --enablerepo for temporary usage:
yum-config-manager --disable Starlingx-
or
subscription-
5. Configure the failing repository to be skipped, if it is unavailable.
Note that yum will try to contact the repo. when it runs most commands,
so will have to try and fail each time (and thus. yum will be be much
slower). If it is a very temporary problem though, this is often a nice
compromise:
yum-config-manager --save --setopt=
failure: repodata/
http://
Test Activity
-------------
Build
Changed in starlingx: | |
status: | Triaged → In Progress |
In the Dockerfile, we are trying to run....
RUN yum install -y golang
after we install StarlingX repos into /etc/yum.repos.d/
COPY centos- mirror- tools/yum. repos.d/ * /etc/yum.repos.d/
It should be before!
A second question is why do we install StarlingX repos into /etc/yum.repos.d/ at all?
Doesn't yumdownloader support --config flag?