Improve oVirt proxy

Activity

Show:
Eyal Edri
July 21, 2016, 2:42 PM

looks like another issue with mirror/proxy?

+ yum -y install postgresql-server
Loaded plugins: fastestmirror, versionlock

One of the configured repositories failed (Unknown),
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. Disable the repository, 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 <repoid>

4. 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=<repoid>.skip_if_unavailable=true

Cannot find a valid baseurl for repo: base/7/x86_64
Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
12: Timeout on http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')
+ show_error
+ [[ SETUP::INIT_POSTGRES == \F\I\N\I\S\H\E\D ]]
+ echo 'FAILED::SETUP::INIT_POSTGRES:: Unrecoverable failure, exitting'
FAILED::SETUP::INIT_POSTGRES:: Unrecoverable failure, exitting
Build step 'Execute shell' marked build as failure
Performing Post build task...

Evgheni Dereveanchin
July 21, 2016, 2:58 PM

The error here is related to mirrorlist.centos.org:

Cannot find a valid baseurl for repo: base/7/x86_64
Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
12: Timeout on http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')

So at least the fault here is not in repoproxy.py as this mirror is not served by it. In fact, I did not find any requests from the build machine (el7-vm01.phx.ovirt.org) to the proxy within the last couple of hours (since 9:50 AM GMT) so this particular job may not be using the proxy at all and connects to repos directly. I'm not very familiar with job configuration structure, can we confirm this somehow?

danken
July 22, 2016, 11:24 AM

On Thu, Jul 21, 2016 at 10:29:51AM -0400, Martin Mucha wrote:
> false CI-1
>
> http://jenkins.ovirt.org/job/ovirt-engine_master_upgrade-from-4.0_el7_created/87/console

Thanks for reporting these.

But could you take a deeper look and help the infra team understand what
broke there?

The console log is removed after a few days, so you should better give a
short excerpt about what broken.

In this case the core problem is:

Cannot find a valid baseurl for repo: base/7/x86_64
Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was
12: Timeout on http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock: (28, 'Operation too slow. Less than 1000 bytes/sec transferred the last 30 seconds')

Eyal Edri
July 25, 2016, 2:41 PM

I believe this was due to broken centos mirror which was fixed after reruning the job using another mirror.
is looking into improving our proxy which might help eliminate those errors, for the short term - if you see errors like:

"Could not retrieve mirrorlist http://mirrorlist.centos.org/?release=7&arch=x86_64&repo=os&infra=stock error was" please try to retry the job, that should fix the issue most of the times until we'll have a better way to handle broken mirrors (which isn't managed by us, so basically this can happen to anyone using those repos)

Eyal Edri
August 21, 2016, 3:01 PM

duplicate #645

Duplicate

Assignee

Evgheni Dereveanchin

Reporter

Martin Mucha

Blocked By

None

Priority

Medium