You are viewing a plain text version of this content. The canonical link for it is here.
Posted to infrastructure-issues@apache.org by "Bill Farner (JIRA)" <ji...@apache.org> on 2015/03/17 03:52:39 UTC

[jira] [Resolved] (INFRA-9019) Investigate apparent network issues on jenkins slaves

     [ https://issues.apache.org/jira/browse/INFRA-9019?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Bill Farner resolved INFRA-9019.
--------------------------------
    Resolution: Fixed

Early results look overwhelmingly positive - i have not seen a failure of this since this morning for Mesos or Aurora.  I'm closing the ticket since by all measures we have it seems to be fixed.  Thanks for the help!

> Investigate apparent network issues on jenkins slaves
> -----------------------------------------------------
>
>                 Key: INFRA-9019
>                 URL: https://issues.apache.org/jira/browse/INFRA-9019
>             Project: Infrastructure
>          Issue Type: Task
>          Components: Jenkins
>            Reporter: Bill Farner
>            Assignee: Andrew Bayer
>
> We have two jenkins jobs, both of which seem to experience sporadic network issues.  Our build job pretty routinely times out resolving artifacts, and our review bot occasionally (~every few days) fails with a DNS resolution error.
> The build bot experienced three failures in a row:
> {noformat}
> Failed > Console Output  #759	Jan 14, 2015 8:08:07 PM	 
> Failed > Console Output  #758	Jan 14, 2015 7:08:47 PM	 
> Failed > Console Output  #757	Jan 14, 2015 5:51:01 PM
> {noformat}
> These three builds ran on ubuntu-1, ubuntu-5, and ubuntu-6, respectively.
> They all failed while trying to resolve reviews.apache.org:
> {noformat}
> Traceback (most recent call last):
>   File "./build-support/jenkins/review_feedback.py", line 211, in <module>
>     main()
>   File "./build-support/jenkins/review_feedback.py", line 158, in main
>     if not _needs_reply(server, request):
>   File "./build-support/jenkins/review_feedback.py", line 94, in _needs_reply
>     latest_diff = _get_latest_diff_time(server, request)
>   File "./build-support/jenkins/review_feedback.py", line 73, in _get_latest_diff_time
>     diffs = server.get_resource(request['links']['diffs']['href'])['diffs']
>   File "./build-support/jenkins/review_feedback.py", line 51, in get_resource
>     return json.loads(self.get_resource_data(href, args=args, data=data))
>   File "./build-support/jenkins/review_feedback.py", line 44, in get_resource_data
>     result = urllib2.urlopen(request, data=data)
>   File "/usr/lib/python2.7/urllib2.py", line 127, in urlopen
>     return _opener.open(url, data, timeout)
>   File "/usr/lib/python2.7/urllib2.py", line 404, in open
>     response = self._open(req, data)
>   File "/usr/lib/python2.7/urllib2.py", line 422, in _open
>     '_open', req)
>   File "/usr/lib/python2.7/urllib2.py", line 382, in _call_chain
>     result = func(*args)
>   File "/usr/lib/python2.7/urllib2.py", line 1222, in https_open
>     return self.do_open(httplib.HTTPSConnection, req)
>   File "/usr/lib/python2.7/urllib2.py", line 1184, in do_open
>     raise URLError(err)
> urllib2.URLError: <urlopen error [Errno -2] Name or service not known>
> {noformat}
> I'm wondering if logs on these systems indicate any network issues around these times.



--
This message was sent by Atlassian JIRA
(v6.3.4#6332)