Project

Profile

Help

Issue #8341

closed

Cannot connect to host fixtures.pulpproject.org:443 ssl:default [Name or service not known]

Added by daviddavis over 1 year ago. Updated 11 months ago.

Status:
CLOSED - DUPLICATE
Priority:
Normal
Assignee:
-
Category:
-
Sprint/Milestone:
-
Start date:
Due date:
Estimated time:
Severity:
2. Medium
Version:
Platform Release:
OS:
Triaged:
Yes
Groomed:
No
Sprint Candidate:
No
Tags:
Sprint:
Quarter:

Description

Ticket moved to GitHub: "pulp/pulpcore/1978":https://github.com/pulp/pulpcore/issues/1978


Started background task /pulp/api/v3/tasks/35361c21-4459-4e30-8494-dc2270611e57/
.........Error: Task /pulp/api/v3/tasks/35361c21-4459-4e30-8494-dc2270611e57/ failed: 'Cannot connect to host fixtures.pulpproject.org:443 ssl:default [Name or service not known]'
Actions #2

Updated by fao89 over 1 year ago

  • Triaged changed from No to Yes
Actions #3

Updated by gerrod over 1 year ago

I have this issue occur when I set a sync to use policy 'immediate'. I think it might have to do with the DownloadFactory.

Actions #4

Updated by ggainey over 1 year ago

Another couple transient DNS failures during a test-run:

Mar 10 18:36:19 pulp2-nightly-pulp3-source-centos7.padre-fedora.example.com rq[7244]: raise ClientConnectorError(req.connection_key, exc) from exc Mar 10 18:36:19 pulp2-nightly-pulp3-source-centos7.padre-fedora.example.com rq[7244]: aiohttp.client_exceptions.ClientConnectorError: Cannot connect to host fixtures.pulproject.org:443 ssl:default [Name or service not known]

Time is in UTC.

Actions #5

Updated by misc over 1 year ago

So there was a typo in the openshift deployment, which is now fixed (if all go well).

However, that do not solve the initial issue, who didn't seems to have a typo.

Actions #6

Updated by pulpbot 11 months ago

  • Description updated (diff)
  • Status changed from NEW to CLOSED - DUPLICATE

Also available in: Atom PDF