#12174 build-planet container is failing
Closed: Fixed 24 days ago by phsmoura. Opened a month ago by zlopez.

Describe what you would like us to do:


I noticed today that the build-planet container is failing with

HTTPSConnectionPool(host='duckalignment.academy', port=443): Max retries exceeded with url: /feed (Caused by NewConnectionError('<urllib3.connection.HTTPSConnection object at 0x7f4217019370>: Failed to establish a new connection: [Errno -5] No address associated with hostname'))
HTTPSConnectionPool(host='blog.asleson.org', port=443): Max retries exceeded with url: /index.xml (Caused by SSLError(SSLCertVerificationError(1, '[SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed: certificate has expired (_ssl.c:1000)')))
User jens has a RSS URL but no website.
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/fedora_messaging/api.py", line 327, in publish
    eventual_result.wait(timeout=timeout)
  File "/usr/local/lib/python3.12/site-packages/crochet/_eventloop.py", line 194, in wait
    result = self._result(timeout)
             ^^^^^^^^^^^^^^^^^^^^^
  File "/usr/local/lib/python3.12/site-packages/crochet/_eventloop.py", line 173, in _result
    raise TimeoutError()
crochet._eventloop.TimeoutError

The above exception was the direct cause of the following exception:

Traceback (most recent call last):
  File "/pluto/build_planet.py", line 149, in <module>
    api.publish(
  File "/usr/local/lib/python3.12/site-packages/fedora_messaging/api.py", line 333, in publish
    raise wrapper from e
fedora_messaging.exceptions.PublishTimeout: Publishing timed out after waiting 30 seconds.
Exception ignored in: <function EventualResult.__del__ at 0x7f421814b380>
Traceback (most recent call last):
  File "/usr/local/lib/python3.12/site-packages/crochet/_eventloop.py", line 139, in __del__
  File "/usr/lib64/python3.12/threading.py", line 611, in isSet
ImportError: sys.meta_path is None, Python is likely shutting down

It ends up in crashloop because of that.

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


I'm not sure how urgent this is as the planet pod itself works fine.


Metadata Update from @zlopez:
- Issue priority set to: Waiting on Assignee (was: Needs Review)
- Issue tagged with: Needs investigation, ops

a month ago

Well the planet pod is just serving the content. The cronjobs update it. So, with those crashing it likely isn't updating. ;(

It was breaking when calling fedora message in the script. It was solved with issue 12032

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

24 days ago

Log in to comment on this ticket.

Metadata
Boards 1
ops Status: Backlog