#9008 the-new-hotness can't connect to bugzilla on iad2
Closed: Fixed 4 years ago by zlopez. Opened 4 years ago by zlopez.

Describe what you would like us to do:


When deploying the-new-hotness on iad2 I noticed that it's not able to connect to bugzilla.redhat.com. Following is the full traceback:

[fedora_messaging.cli INFO] Starting consumer with hotness.consumers:BugzillaTicketFiler callback
[hotness.bz INFO] Using BZ URL https://bugzilla.redhat.com 
Traceback (most recent call last):
  File "/usr/lib/python3.8/site-packages/urllib3/connection.py", line 156, in _new_conn
    conn = connection.create_connection(
  File "/usr/lib/python3.8/site-packages/urllib3/util/connection.py", line 84, in create_connection
    raise err
  File "/usr/lib/python3.8/site-packages/urllib3/util/connection.py", line 74, in create_connection
    sock.connect(sa)
TimeoutError: [Errno 110] Connection timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", line 665, in urlopen
    httplib_response = self._make_request(
  File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", line 376, in _make_request
    self._validate_conn(conn)
  File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", line 994, in _validate_conn
    conn.connect()
  File "/usr/lib/python3.8/site-packages/urllib3/connection.py", line 334, in connect
    conn = self._new_conn()
  File "/usr/lib/python3.8/site-packages/urllib3/connection.py", line 168, in _new_conn
    raise NewConnectionError(
urllib3.exceptions.NewConnectionError: <urllib3.connection.VerifiedHTTPSConnection object at 0x7f2040f190a0>: Failed to establish a new connection: [Errno 110] Connection timed out

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/lib/python3.8/site-packages/requests/adapters.py", line 439, in send
    resp = conn.urlopen(
  File "/usr/lib/python3.8/site-packages/urllib3/connectionpool.py", line 719, in urlopen
    retries = retries.increment(
  File "/usr/lib/python3.8/site-packages/urllib3/util/retry.py", line 436, in increment
    raise MaxRetryError(_pool, url, error or ResponseError(cause))
urllib3.exceptions.MaxRetryError: HTTPSConnectionPool(host='bugzilla.redhat.com', port=443): Max retries exceeded with url: /xmlrpc.cgi (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f2040f190a0>: Failed to establish a new connection: [Errno 110] Connection timed out'))

During handling of the above exception, another exception occurred:

Traceback (most recent call last):
  File "/usr/bin/fedora-messaging", line 11, in <module>
    load_entry_point('fedora-messaging==2.0.1', 'console_scripts', 'fedora-messaging')()
  File "/usr/lib/python3.8/site-packages/click/core.py", line 829, in __call__
    return self.main(*args, **kwargs)
  File "/usr/lib/python3.8/site-packages/click/core.py", line 782, in main
    rv = self.invoke(ctx)
  File "/usr/lib/python3.8/site-packages/click/core.py", line 1259, in invoke
    return _process_result(sub_ctx.command.invoke(sub_ctx))
  File "/usr/lib/python3.8/site-packages/click/core.py", line 1066, in invoke
    return ctx.invoke(self.callback, **ctx.params)
  File "/usr/lib/python3.8/site-packages/click/core.py", line 610, in invoke
    return callback(*args, **kwargs)
  File "/usr/lib/python3.8/site-packages/fedora_messaging/cli.py", line 120, in consume
    _consume(exchange, queue_name, routing_key, callback, app_name)
  File "/usr/lib/python3.8/site-packages/fedora_messaging/cli.py", line 163, in _consume
    deferred_consumers = api.twisted_consume(
  File "/usr/lib/python3.8/site-packages/fedora_messaging/api.py", line 150, in twisted_consume
    callback = _check_callback(callback)
  File "/usr/lib/python3.8/site-packages/fedora_messaging/api.py", line 74, in _check_callback
    callback_object = callback()
  File "/usr/local/lib/python3.8/site-packages/hotness/consumers.py", line 67, in __init__
    self.bugzilla = hotness.bz.Bugzilla(
  File "/usr/local/lib/python3.8/site-packages/hotness/bz.py", line 68, in __init__
    self.bugzilla = bugzilla.Bugzilla(
  File "/usr/lib/python3.8/site-packages/bugzilla/base.py", line 306, in __init__
    self.connect(url)
  File "/usr/lib/python3.8/site-packages/bugzilla/base.py", line 553, in connect
    version = self._proxy.Bugzilla.version()["version"]
  File "/usr/lib64/python3.8/xmlrpc/client.py", line 1109, in __call__
    return self.__send(self.__name, args)
  File "/usr/lib/python3.8/site-packages/bugzilla/transport.py", line 103, in _ServerProxy__request
    ret = super(_BugzillaServerProxy,
  File "/usr/lib64/python3.8/xmlrpc/client.py", line 1450, in __request
    response = self.__transport.request(
  File "/usr/lib/python3.8/site-packages/bugzilla/transport.py", line 202, in request
    return self._request_helper(url, request_body)
  File "/usr/lib/python3.8/site-packages/bugzilla/transport.py", line 164, in _request_helper
    response = self.session.post(
  File "/usr/lib/python3.8/site-packages/requests/sessions.py", line 581, in post
    return self.request('POST', url, data=data, json=json, **kwargs)
  File "/usr/lib/python3.8/site-packages/requests/sessions.py", line 533, in request
    resp = self.send(prep, **send_kwargs)
  File "/usr/lib/python3.8/site-packages/requests/sessions.py", line 646, in send
    r = adapter.send(request, **kwargs)
  File "/usr/lib/python3.8/site-packages/requests/adapters.py", line 516, in send
    raise ConnectionError(e, request=request)
requests.exceptions.ConnectionError: HTTPSConnectionPool(host='bugzilla.redhat.com', port=443): Max retries exceeded with url: /xmlrpc.cgi (Caused by NewConnectionError('<urllib3.connection.VerifiedHTTPSConnection object at 0x7f2040f190a0>: Failed to establish a new connection: [Errno 110] Connection timed out'))

When do you need this to be done by? (YYYY/MM/DD)



We have had this in the past where we needed to define the equivalent of an
/etc/hosts to reach out to bugzilla. Could it be the case here as well?

I checked the pod now and it's working without issue, so I'm closing this as fixed.

Metadata Update from @zlopez:
- Issue close_status updated to: Fixed
- Issue status updated to: Closed (was: Open)

4 years ago

Log in to comment on this ticket.

Metadata