Importing the container image offline-knowledge-portal/rhokp-rhel9 fails when syncing the repository with:

Response payload is not completed: <ContentLengthError: 400, message='Not enough data for satisfy content length header.'>

Steps to reproduce:

1. Follow steps 1 to 5 from the docs
2. In the Registry Search Parameter field, enter `offline-knowledge-portal/rhokp-rhel9`, and then click Discover.
3. From the Discovered Repository list, select the repository to import, and then click Create Selected.
4. In the Name field, enter: Red Hat Offline Knowledge Portal
5. Click Run Repository Creation.
6. When repository creation is complete, you can click each new repository to view more information.
7. In the Satellite web UI, navigate to Content > Products and select the name of your product (Red Hat Offline Knowledge Portal).
8. Select the new repositories and then click Sync Now to start the synchronization process.

Results in Satellite 6.17.6:

Error:

Response payload is not completed: <ContentLengthError: 400, message='Not enough data for satisfy content length header.'>

Please see attachment 'sat_6.17.txt' for more full output and backtrace.

Results in Satellite 6.18.1:

Actions::BulkAction

{"action_class"=>"Actions::Katello::Repository::Sync",
 "target_ids"=>[38],
 "target_class"=>"Katello::Repository",
 "args"=>[],
 "kwargs"=>{},
 "current_request_id"=>"126ac02f-5478-480a-b25c-f7a4db843a46",
 "current_timezone"=>"Europe/Berlin",
 "current_organization_id"=>1,
 "current_location_id"=>2,
 "current_user_id"=>4,
 "dynflow"=>{}}

{"planned_count"=>1,
 "cancelled_count"=>0,
 "total_count"=>1,
 "failed_count"=>1,
 "pending_count"=>0,
 "success_count"=>0}

Dynflow::Action::V2::WithSubPlans::SubtaskFailedException: A sub task failed

Expectd result:

The import should complete successfully.

Why does the customer need this?

The hosts in the customer's environment are not allowed to access the internet. Satellite is used to import container images to provide them to other hosts on the network. With this issue present the customer is not able to deploy the Red Hat Offline Knowledge Portal in the desired way.