Bug 2064945

Summary: Disconnected Satellite 6.10.2 servers cannot import content from connected Satellite 6.10.3 servers
Product: Red Hat Satellite Reporter: Jessica Hanley <jhanley>
Component: PulpAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: Lai <ltran>
Severity: high Docs Contact:
Priority: high    
Version: 6.10.2CC: ahumbe
Target Milestone: UnspecifiedKeywords: PrioBumpGSS, Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2022-04-25 05:29:00 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description Jessica Hanley 2022-03-16 21:54:20 UTC 
Description of problem:

If content is exported from a Satellite 6.10.3 server, and then customers try to import it into a disconnected Satellite 6.10.2 server, they get errors like these:

[ErrorDetail(string='Export version 3.14.9 of pulpcore does not match installed version 3.14.12.', code='invalid')]

Error: [ErrorDetail(string='Export version 3.14.12 of pulp_rpm does not match installed version 3.14.7.', code='invalid')]


How reproducible:

100%


Steps to Reproduce:
1.  export a content view from a Satellite 6.10.3 server
2.  try to import that content view into a disconnected Satellite 6.10.2 server

Actual results:

The content will not import.


Expected results:

The content should import as long as the source is of the same major version.



Additional info:

While disconnected servers can be upgraded via ISO, our ISO images are often out of date.  Customers could easily face dependency hell trying to import content into their disconnected servers if they install an RHSA on their connected Satellite server, but then find that our ISO images don't contain the packages from that RHSA.
Comment 1 Ashish Humbe 2022-04-25 05:29:00 UTC 

*** This bug has been marked as a duplicate of bug 2067301 ***