Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Descriptionsthirugn@redhat.com
2019-04-11 13:20:49 UTC
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
Verified fix in sat 6.5 snap 24.
Follow the steps the in the description and the puppet modules got synced to the capsule:
[root@capsule ~]# ls /etc/puppetlabs/code/environments/KT_Default_Organization_Library_testcv_5/modules/stdlib/
appveyor.yml checksums.json examples HISTORY.md LICENSE MAINTAINERS.md metadata.json Rakefile README.md README_SPECS.markdown spec
CHANGELOG.md CONTRIBUTING.md Gemfile lib locales manifests NOTICE README_DEVELOPER.markdown readmes RELEASE_PROCESS.markdown types
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/RHSA-2019:1222