Description of problem:
Puppet environments are not synced to the capsules

Version-Release number of selected component (if applicable):
satellite-6.5.0-11.el7sat.noarch

How reproducible:
Always

Steps to Reproduce:

On Satellite:
*************
# hammer capsule list
---|-------------------------------------------------|--------------------------------------------------------------|--------------------------
ID | NAME                                            | URL                                                          | FEATURES                 
---|-------------------------------------------------|--------------------------------------------------------------|--------------------------
2  | pipeline-capsule-6-5-rhel7.kangae.example.com   | https://pipeline-capsule-6-5-rhel7.kangae.example.com:9090   | Templates, Pulp Node, ...
1  | pipeline-satellite-6-5-rhel7.kangae.example.com | https://pipeline-satellite-6-5-rhel7.kangae.example.com:9090 | Templates, Pulp, TFTP,...
---|-------------------------------------------------|--------------------------------------------------------------|--------------------------

# hammer capsule content add-lifecycle-environment --environment Library --id 2 --organization "Default Organization"
Lifecycle environment successfully added to the capsule.

[root@pipeline-satellite-6-5-rhel7 ~]# hammer product create --name testprod --organization "Default Organization"
Product created.

# hammer repository create --name testrepo --content-type puppet --product testprod --organization "Default Organization"
Repository created.

# hammer repository upload-content --name testrepo --product testprod --organization "Default Organization" --path  puppetlabs-stdlib-5.2.0.tar.gz
Successfully uploaded file 'puppetlabs-stdlib-5.2.0.tar.gz'

# hammer content-view create --name testcv --organization "Default Organization"
Content view created.

# hammer content-view puppet-module add --author puppetlabs --name stdlib --content-view testcv --organization "Default Organization"
Puppet module added to content view.

# hammer content-view puppet-module list --content-view testcv --organization "Default Organization"
-----|--------|------------|------------------------
UUID | NAME   | AUTHOR     | VERSION                
-----|--------|------------|------------------------
     | stdlib | puppetlabs | Latest(Currently 5.2.0)
-----|--------|------------|------------------------

# ls /etc/puppetlabs/code/environments/
common  development  KT_Test_Organization_Library_Test_CV_4  KT_Test_Organization_Test_Test_CV_4  production

$ ls /etc/puppetlabs/code/environments/
common  development  production

# hammer content-view publish --name testcv --organization "Default Organization"
[.........................................................................................] [100%]

# ls /etc/puppetlabs/code/environments/
common  development  KT_Default_Organization_Library_testcv_5  KT_Test_Organization_Library_Test_CV_4  KT_Test_Organization_Test_Test_CV_4  production

On Capsule:
************
# ls /etc/puppetlabs/code/environments/
common  development  production

Actual results:
The capsules doesn't get the new puppet environments created by Satellite's content view with puppet modules in them.

Expected results:
The capsules must get the new puppet environments created by Satellite's content view with puppet modules in them.

Additional info:
This works fine in Satellite 6.4