Project

General

Profile

Actions

Bug #35616

closed

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

Added by Richard Stempfl over 1 year ago. Updated over 1 year ago.

Status:
Closed
Priority:
Normal
Assignee:
-
Category:
API
Target version:
-
Difficulty:
Triaged:
Yes
Fixed in Releases:
Found in Releases:

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"}" 

Files

api_error.txt api_error.txt 16.2 KB log Richard Stempfl, 10/13/2022 08:01 AM
Actions #1

Updated by Partha Aji over 1 year 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.

Actions #2

Updated by Richard Stempfl over 1 year 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

Actions #3

Updated by Lucy Fu over 1 year ago

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

Updated by Samir Jha over 1 year 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.

Actions #5

Updated by Chris Roberts over 1 year ago

  • Target version changed from Katello 4.7.0 to Katello 4.8.0
Actions #6

Updated by Samir Jha over 1 year ago

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

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.

Actions #7

Updated by William Clark over 1 year ago

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

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,

Actions

Also available in: Atom PDF