#1052 succeeded build marked as failed again
Closed: Fixed 4 years ago by msuchy. Opened 4 years ago by praiskup.


Metadata Update from @praiskup:
- Issue tagged with: bug

4 years ago
Traceback (most recent call last):
  File "/usr/lib/python3.7/site-packages/urllib3/connection.py", line 157, in _new_conn
    (self._dns_host, self.port), self.timeout, **extra_kw)
  File "/usr/lib/python3.7/site-packages/urllib3/util/connection.py", line 80, in create_connection
    raise err
  File "/usr/lib/python3.7/site-packages/urllib3/util/connection.py", line 70, in create_connection
    sock.connect(sa)
ConnectionRefusedError: [Errno 111] Connection refused

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.7/site-packages/urllib3/connectionpool.py", line 600, in urlopen
    chunked=chunked)
  File "/usr/lib/python3.7/site-packages/urllib3/connectionpool.py", line 343, in _make_request
    self._validate_conn(conn)
  File "/usr/lib/python3.7/site-packages/urllib3/connectionpool.py", line 839, in _validate_conn
    conn.connect()
  File "/usr/lib/python3.7/site-packages/urllib3/connection.py", line 299, in connect
    conn = self._new_conn()
  File "/usr/lib/python3.7/site-packages/urllib3/connection.py", line 166, in _new_conn
    self, "Failed to establish a new connection: %s" % e)
urllib3.exceptions.NewConnectionError: <urllib3.connection.VerifiedHTTPSConnection object at 0x7f1eaf0b3d50>: Failed to establish a new connection: [Errno 111] Connection refused

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.7/site-packages/requests/adapters.py", line 449, in send
    timeout=timeout
  File "/usr/lib/python3.7/site-packages/urllib3/connectionpool.py", line 638, in urlopen
    _stacktrace=sys.exc_info()[2])
  File "/usr/lib/python3.7/site-packages/urllib3/util/retry.py", line 399, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='copr.fedorainfracloud.org', port=443): Max retries exceeded with url: /api/coprs/jdanecki/intel-opencl-tests/detail/ (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f1eaf0b3d50>: Failed to establish a new connection: [Errno 111] Connection refused'))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.7/site-packages/copr/client/client.py", line 258, in _fetch
    **kwargs
  File "/usr/lib/python3.7/site-packages/requests/api.py", line 60, in request
    return session.request(method=method, url=url, **kwargs)
  File "/usr/lib/python3.7/site-packages/requests/sessions.py", line 533, in request
    resp = self.send(prep, **send_kwargs)
  File "/usr/lib/python3.7/site-packages/requests/sessions.py", line 646, in send
    r = adapter.send(request, **kwargs)
  File "/usr/lib/python3.7/site-packages/requests/adapters.py", line 516, in send
    raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='copr.fedorainfracloud.org', port=443): Max retries exceeded with url: /api/coprs/jdanecki/intel-opencl-tests/detail/ (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f1eaf0b3d50>: Failed to establish a new connection: [Errno 111] Connection refused'))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/share/copr/backend/daemons/worker.py", line 239, in do_job
    mr.on_success_build()
  File "/usr/share/copr/backend/mockremote/__init__.py", line 242, in on_success_build
    self.do_createrepo()
  File "/usr/share/copr/backend/mockremote/__init__.py", line 220, in do_createrepo
    project_owner, project_name)
  File "/usr/share/copr/backend/helpers.py", line 303, in uses_devel_repo
    result = client.get_project_details(projectname, username)
  File "/usr/lib/python3.7/site-packages/copr/client/client.py", line 1153, in get_project_details
    data = self._fetch(url, skip_auth=True)
  File "/usr/lib/python3.7/site-packages/copr/client/client.py", line 263, in _fetch
    raise CoprRequestException("Connection error {0} {1}".format(method.upper(), url))
copr.exceptions.CoprRequestException: Connection error GET https://copr.fedorainfracloud.org/api/coprs/jdanecki/intel-opencl-tests/detail/

We either need to make the uses_devel_repo() method resilient, and re-try there indefinitely till frontend becomes available again ... or simply put the "uses_devel_repo" info into the task info (which is provided by /backend/ API namespace in advance). That way we wouldn't have to rely on copr-cli at all in backend.

I'd prefer to move this into task info, WDYT? @frostyx @msuchy

I'd prefer to move this into task info, WDYT? @frostyx @msuchy

Me too

Hmpfs, actions suffer from the same problem.

Metadata Update from @frostyx:
- Issue assigned to frostyx

4 years ago

I've created PR#1078 which fixes the build issue by moving the uses_devel_repo directly to the task info.

Hmpfs, actions suffer from the same problem.

However, this approach doesn't make much sense for actions. So, should we reconsider the

We either need to make the uses_devel_repo() method resilient, and re-try there indefinitely till frontend becomes available again ..

idea and use it for actions (or in that case discard even the PR#1078 and solve the issue the same way for builds). Do you have any ideas?

Log in to comment on this ticket.

Metadata
Related Pull Requests
  • #1078 Merged 4 years ago