Description of problem:

While performing incremental update using hammer command, it doesn't add any content for the particular packages/erratas in Satellite 6.15 and Satellite 6.16 but surprisingly in Satellite 6.17 it added for one time with a package and while further tested, it didn't add anymore whether it's package or errata even with the other content views as well. Once performed the incremental update, it generates a new minor version for sure but with all the packages as they were present in the major version. 

How reproducible:

Always

Is this issue a regression from an earlier version:

Yes

Steps to Reproduce:

1.  Create a content view and add repositories over the same and publish a new version and promote into 'Library' environment so let's say the version is now 1.0.

2. Execute the commands as below on the Satellite server.

~~~

1. hammer package list {}search "<package_name>"    <{}- To note the ID of any package from the added repositories to add as an incremental update.

1. hammer content-view version list  <--- To get the ID of the particular version.

1. hammer content-view version incremental-update {}content-view-version-id <id> -package-ids <id> --lifecycle-environments '<env>' --organization-id <id>   <--- To perform the incremental update. 

~~~

Actual behavior:

1. hammer content-view version incremental-update --content-view-version-id 28 --package-ids 119594 --lifecycle-environments 'Library' --organization-id 1
   [......................................................................................................................] [100%]
   Content View: TEST version 4.1
   Added Content:
2. # hammer content-view version incremental-update --content-view-version-id 19 --errata-ids 13116 --lifecycle-environments 'Library' --organization-id 1
   [......................................................................................................................] [100%]
   Content View: rhel9 version 9.2
   Added Content:
    

1. hammer content-view version info --id 29
   Id:                     29
   Name:                   TEST 4.1
   Version:                4.1
   Description:            
   Content View ID:        12
   Content View Name:      TEST
   Content View Label:     TEST
   Lifecycle Environments: 
    
   Repositories:           
   1) Id:    106
   Name:  Red Hat Enterprise Linux 9 for x86_64 - BaseOS RPMs 9
   Label: Red_Hat_Enterprise_Linux_9_for_x86_64_-_BaseOS_RPMs_9
    2) Id:    107
   Name:  Red Hat Enterprise Linux 9 for x86_64 - AppStream RPMs 9
   Label: Red_Hat_Enterprise_Linux_9_for_x86_64_-_AppStream_RPMs_9
   Has Applied Filters:    no
   {}{}
   Expected behavior:

1. hammer content-view version incremental-update --content-view-version-id '13' --package-ids '858' --lifecycle-environments 'Library' --organization-id '1'
   [......................................................................................................................] [100%]
   Content View: rhel9 version 6.1
   Added Content:
     RPM Packages:
   katello-pull-transport-migrate-1.0.3-1.el9sat.noarch
    

1. hammer content-view version info --id 14
   Id:                     14
   Name:                   rhel9 6.1
   Version:                6.1
   Description:            Packages:
       katello-pull-transport-migrate-1.0.3-1.el9sat.noarch
   Content View ID:        2
   Content View Name:      rhel9
   Content View Label:     rhel9
   Lifecycle Environments: 

Repositories:           
 1) Id:    46
    Name:  Red Hat Satellite Client 6 for RHEL 9 x86_64 RPMs
    Label: Red_Hat_Satellite_Client_6_for_RHEL_9_x86_64_RPMs
Has Applied Filters:    yes

Business Impact / Additional info:

No operational impact as of now but Customer is using this feature and they are stuck with the same.