Project

General

Profile

Bug #35616

Api /katello/api/repositories/:repository_id/sync fails

Added by Richard Stempfl 4 months ago. Updated 3 months ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
API
Target version:
-
Difficulty:
Triaged:
Yes
Bugzilla link:
Pull request:
Fixed in Releases:
Katello 4.6.0
Found in Releases:
Katello 4.3.1
Red Hat JIRA:

Description

The api call of
GET /katello/api/repositories/:repository_id/sync

fails with the following message:

"fatal: [localhost]: FAILED! => {"changed": false, "error": {"displayMessage": "unknown keyword: :use_admin_as_cn_pulp_cert", "errors": ["unknown keyword: :use_admin_as_cn_pulp_cert"]}, "msg": "Unable to list resource: HTTPError: 500 Server error: Internal server error for url: https://FQDN/katello/api/repositories/12/sync"}"
api_error.txt api_error.txt 16.2 KB log Richard Stempfl, 10/13/2022 08:01 AM

History

#1 Updated by Partha Aji 4 months ago

  • Status changed from New to Need more information

Hey Richard.
Can you give us more production logs when this error occurs.
Might wanna upgrade to a later Katello version :). Katello 4.3 is unsupported at this point.

#2 Updated by Richard Stempfl 4 months ago

Hi,

I have attached a foreman-tail during the execution.

Switching to a newer Version is not possible at the moment.

Is this already fixed in a future versions?

Thx

#3 Updated by Lucy Fu 4 months ago

  • Triaged changed from No to Yes
  • Target version set to Katello 4.7.0
  • Status changed from Need more information to New
  • Category set to API

#4 Updated by Samir Jha 3 months ago

  • Fixed in Releases Katello 4.6.0 added

Hey Richard,

This has been fixed in 4.6. We don't use the param use_admin_as_cn_pulp_cert anymore.

#5 Updated by Chris Roberts 3 months ago

  • Target version changed from Katello 4.7.0 to Katello 4.8.0

#6 Updated by Samir Jha 3 months ago

  • Triaged changed from Yes to No
  • Target version deleted (Katello 4.8.0)
  • Status changed from New to Need more information

Hey Richard,

Let us know if you are still seeing this. The API endpoint has changed in 4.6 and onwards so this is no longer an issue in newer releases.

#7 Updated by William Clark 3 months ago

  • Triaged changed from No to Yes
  • Status changed from Need more information to Closed

Hi Richard,

We decided to close this one since that API is changed on 4.6+ anyway. If you want to try fixing it on 4.5, please feel free to re-open.

Thanks,

Also available in: Atom PDF