This issue seems related to the node functionality and gofer parts of capsule syncing. In Satellite 6.2 we are no longer using these parts of pulp to perform the syncing. Moving to modified.
Verified with sat6.2 beta snap6 I can sync puppet modules between satellite and capsule. - I created a puppet_cv and added 'apache' and 'nova' modules. - published/promoted them to 'test' env - ran capsule sync as below. on satellite server: Following two modules are synced ==================== [root@cloud-qe-15 ~]# getenforce Enforcing [root@cloud-qe-15 ~]# grep '"version":' /etc/puppet/environments/KT_Default_Organization_Test_puppet_cv_8/modules/apache/metadata.json "version": "1.8.1", [root@cloud-qe-15 ~]# grep '"version":' /etc/puppet/environments/KT_Default_Organization_Test_puppet_cv_8/modules/nova/metadata.json "version": "7.0.0", [root@cloud-qe-15 ~]# hammer -u admin -p changeme capsule content synchronize --id 2 [............................................................................................................................................] [100%] on capsule, after sync: ======================= [root@cloud-qe-7 ~]# getenforce Enforcing [root@cloud-qe-7 ~]# grep '"version":' /etc/puppet/environments/KT_Default_Organization_Test_puppet_cv_8/modules/apache/metadata.json "version": "1.8.1", [root@cloud-qe-7 ~]# grep '"version":' /etc/puppet/environments/KT_Default_Organization_Test_puppet_cv_8/modules/nova/metadata.json "version": "7.0.0",
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2016:1500