Bug #36977: Hammer is not propagating error message from production log when content-export fails - Katello - Foreman

Actions

Copy link

Bug #36977

closed

Hammer is not propagating error message from production log when content-export fails

Added by Chris Roberts 12 months ago. Updated 11 months ago.

Status:

Closed

Priority:

Normal

Assignee:

Chris Roberts

Category:

Inter Server Sync

Target version:

Katello 4.12.0

Difficulty:

easy

Triaged:

Yes

Bugzilla link:

2172845

Pull request:

https://github.com/Katello/katello/pull/10823

Fixed in Releases:

Katello 4.12.0

Found in Releases:

Red Hat JIRA:

SAT-19394

Description

Similar result for different scenario:
1) Create new repo, add content, export complete importable format: hammer content-export complete repository --format importable --organization-id 1 --id <repo_id>
2) Check the export path -> tar.gz exported
3) Upload one rpm.
4) Export incremental syncable format: hammer content-export incremental repository --format syncable --organization-id 1 --id <repo_id>

Actual results:
[root@sat ~]# hammer content-export incremental repository --format syncable --organization-id 1 --id 80
Could not export the repository:
400 Bad Request

production log:
2023-02-23T05:25:37 [E|app|63206f2c] Katello::HttpErrors::BadRequest: Unable to incrementally export. Do a Full Export on the repository content.

Expected results:
[root@sat ~]# hammer content-export incremental repository --format syncable --organization-id 1 --id 80
Could not export the repository:
Unable to incrementally export. Do a Full Export on the repository content.