Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 2052333 - Repository sync sometimes failed with PulpcoreClient::ApiError due to timeout
Summary: Repository sync sometimes failed with PulpcoreClient::ApiError due to timeout
Keywords:
Status: CLOSED DUPLICATE of bug 2033853
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Pulp
Version: 6.10.2
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: Unspecified
Assignee: satellite6-bugs
QA Contact: Lai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-09 01:42 UTC by matt jia
Modified: 2022-02-24 20:12 UTC (History)
1 user (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-02-24 20:12:22 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)

Description matt jia 2022-02-09 01:42:24 UTC 
Description of problem:

When syncing multiple repos in parallel(a sync plan, etc.), some repos failed on 

 16: Actions::Pulp3::Repository::RefreshDistribution (skipped) [ 1459.68s / 189.50s

 Output:

---
pulp_tasks:
- pulp_href: "/pulp/api/v3/tasks/b5964731-7dfc-44af-b2e8-c012b1e39342/"
  pulp_created: '2022-01-31T04:05:31.670+00:00'
  state: waiting 


 Error:

PulpcoreClient::ApiError

Error message: the server returns an error 

However, the task itself completed successfully:

4167:Jan 31 05:31:01 gvecsl8900ipm pulpcore-worker-6: pulp [b84996b9-5e06-4936-a604-91cb3e64436b]: pulpcore.tasking.pulpcore_worker:INFO: Starting task b5964731-7dfc-44af-b2e8-c012b1e39342
14173:Jan 31 05:31:02 gvecsl8900ipm pulpcore-worker-6: pulp [b84996b9-5e06-4936-a604-91cb3e64436b]: pulpcore.tasking.pulpcore_worker:INFO: Task completed b5964731-7dfc-44af-b2e8-c012b1e39342


Version-Release number of selected component (if applicable):

6.10


How reproducible:

Easy

Steps to Reproduce:
1. create a sync plan with 50+ repos
2. trigger the sync plan manually
3.

Actual results:

Some repos failed with  PulpcoreClient::ApiError


Expected results:

All repository sync should finish successfully.

Additional info:

I've opened an issue against pulp-openapi-generator:

https://github.com/pulp/pulp-openapi-generator/issues/61
Note You need to log in before you can comment on or make changes to this bug.