Bug 2048861 - complete content view version export fails to import
Summary: complete content view version export fails to import
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Inter Satellite Sync
Version: 6.10.2
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: 6.12.0
Assignee: satellite6-bugs
QA Contact: Lai
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-02-01 02:12 UTC by Gary Scarborough
Modified: 2022-08-30 18:31 UTC (History)
2 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2022-08-15 18:11:33 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker SAT-8420 0 None None None 2022-08-30 18:31:43 UTC

Description Gary Scarborough 2022-02-01 02:12:02 UTC
Description of problem:

My customer is trying to import an exported content view created on Satellite 6.10.2 into a disconnected Satellite 6.10.2.

The hammer command ends with the error:

Error: 1 subtask(s) failed for task group /pulp/api/v3/task-groups/........



Dynflow shows:

The failed subtask was Actions::Pulp3::ContentViewVersion::Import (error)

The name of the actual failed task is:

pulpcore.app.tasks.importer.import_repository_version



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

Satellite 6.10.1 and 6.10.2


How reproducible:

?  Happens consistently on his satellite.


Steps to Reproduce:
1.
2.
3.

Actual results:

Content import fails


Expected results:

Content should be imported


Additional info:

pdf files of the logs are attached.  Customer is in a secure facility, this is the only way they can give is data.

Comment 4 Gary Scarborough 2022-02-01 04:16:33 UTC
This bug is very close to a bug that I am hitting on my test satellite, BZ 2048876.

On a fresh 6.10.2 install I am unable to export a content view.

Comment 5 Partha Aji 2022-02-07 19:19:57 UTC
This should be fixed by -> https://bugzilla.redhat.com/show_bug.cgi?id=2033847
@Gary - Can you apply the hotfix there in that bugzilla and test again?


Note You need to log in before you can comment on or make changes to this bug.