Description of problem:
Exporting a composite content view with options incremental and syncable will always export the entire content view.

The same behavior is not observed when using a regular content view.

To demonstrate, I created 2 content views, one is a regular content view named cv-test and then one is a composite content view named ccv-test. Both content views only have 2 versions published, and they are identical.

Version 1.0 of both content views only contains the repository:

• Satellite 6.10 for RHEL8.

Version 2.0 of both content views contains the repositories:

• Satellite 6.10 for RHEL8
• Satellite Client 6 for RHEL8

These commands were used to create a complete syncable export for version 1.0 of both content views:

 hammer content-export complete version --content-view cv-test --version 1.0 --format syncable

hammer content-export complete version --content-view ccv-test --version 1.0 --format syncable --organization Yoder

And we see both exports are the same size (which is expected):

[root@satellite ~]# du -sch /var/lib/pulp/exports/Yoder/cv-test/1.0/
2.3G	/var/lib/pulp/exports/Yoder/cv-test/1.0/
2.3G	total

[root@satellite ~]# du -sch /var/lib/pulp/exports/Yoder/ccv-test/1.0/
2.3G	/var/lib/pulp/exports/Yoder/ccv-test/1.0/
2.3G	total

 
Then we add the Satellite Client 6.10 RHEL8 repository and take an incremental export of both content views:

hammer content-export incremental  version --content-view cv-test --version 2.0 --format syncable --organization Yoder

hammer content-export incremental version --content-view ccv-test --version 2.0 --format syncable --organization Yoder

This time the regular content view cv-test has the correct export size for the incremental export of version 2.0. But the composite content view ccv-test incremental export of version 2.0 is wrong, and it shows the size of both repositories, when it should only show the size of the Satellite Client 6.10 RHEL8 repository:

[root@satellite ~]# du -sch /var/lib/pulp/exports/Yoder/cv-test/2.0/
175M	/var/lib/pulp/exports/Yoder/cv-test/2.0/
175M	total

[root@satellite ~]# du -sch /var/lib/pulp/exports/Yoder/ccv-test/2.0/
2.5G	/var/lib/pulp/exports/Yoder/ccv-test/2.0/
2.5G	total

How reproducible:
always
 

Is this issue a regression from an earlier version:
not sure
 

Steps to Reproduce:

1. Create a regular content view and add a relatively large repository that has been synced immediate and publish it.

2. Create a composite content view, and add the regular content view from step 1 to the composite content view, making sure the composite content view is always pointing to the latest version of the regular content view. Publish a new version of the composite content view.

3. Add a smaller repository (one that is synced immediate) to the regular content view and publish a new version.

4. Publish a new version of the composite content view.

5. Take a complete export with format syncable of version 1.0 of both the regular and composite content view.

6. Take an incremental export with format syncable of version 2.0 of both the regular and composite content view.

Actual behavior:
[Describe the issue in detail, including what is happening and where]
The incremental export of the composite content view is larger, and it will be the size of the entire content view, not just what was added to version 2.0.

Expected behavior:
[Describe what should be happening instead]
The incremental export of the composite content view should match the regular content view export for version 2.0. The size of the composite content view for version 2.0 should only be the size of the content added for version 2.0.

Business Impact / Additional info: