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.
Bug 1441781 - CV publishing with puppet module does not add puppet class
Summary: CV publishing with puppet module does not add puppet class
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Satellite
Classification: Red Hat
Component: Content Views
Version: 6.3.0
Hardware: Unspecified
OS: Unspecified
medium
medium
Target Milestone: Unspecified
Assignee: Brad Buckingham
QA Contact: Justin Sherrill
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2017-04-12 17:37 UTC by Stanislav Tkachenko
Modified: 2019-04-01 20:27 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: If docs needed, set a value
Doc Text:
Clone Of:
Environment:
Last Closed: 2018-02-21 16:31:53 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Foreman Issue Tracker 19338 0 None None None 2017-04-20 23:34:05 UTC

Description Stanislav Tkachenko 2017-04-12 17:37:12 UTC 
Description of problem:

On 6.2.z the process of adding puppet classes without creating puppet environments and using puppet manually was:
1. Create product / repo
2. Upload/sync puppet module
3. Add that module to CV
4. Publish CV.

On 6.2 it automagically creates puppet environment and puppet class is listed on Configure/Classes page. On downstream nightly I can see puppet environment but no puppet class.

Version-Release number of selected component (if applicable):
Satellite 6.3/ Downstream nightly
foreman-1.15.0-0.develop
katello-3.4.0-1.nightly

How reproducible:
Always

Steps to Reproduce:
1.
2.
3.

Actual results:
Puppet environment created but it is empty -- no puppet class is available.

Expected results:
After puppet module publishing puppet class should be available on Configure/Classes page.

Additional info:
* candlepin-2.0.30-1.el7.noarch
* candlepin-selinux-2.0.30-1.el7.noarch
* foreman-1.15.0-0.develop.201703271956git40dd32b.el7sat.noarch
* foreman-compute-1.15.0-0.develop.201703271956git40dd32b.el7sat.noarch
* foreman-debug-1.15.0-0.develop.201703271956git40dd32b.el7sat.noarch
* foreman-discovery-image-3.1.1-16.el7sat.noarch
* foreman-ec2-1.15.0-0.develop.201703271956git40dd32b.el7sat.noarch
* foreman-gce-1.15.0-0.develop.201703271956git40dd32b.el7sat.noarch
* foreman-installer-1.15.0-0.develop.201703100324gitb570b53.el7sat.noarch
* foreman-installer-katello-3.5.0-1.nightly.201703312206git730de81.el7sat.noarch
* foreman-libvirt-1.15.0-0.develop.201703271956git40dd32b.el7sat.noarch
* foreman-openstack-1.15.0-0.develop.201703271956git40dd32b.el7sat.noarch
* foreman-ovirt-1.15.0-0.develop.201703271956git40dd32b.el7sat.noarch
* foreman-postgresql-1.15.0-0.develop.201703271956git40dd32b.el7sat.noarch
* foreman-proxy-1.15.0-0.develop.201703271144gitd4ab7f0.el7sat.noarch
* foreman-rackspace-1.15.0-0.develop.201703271956git40dd32b.el7sat.noarch
* foreman-selinux-1.15.0-0.develop.201703200304git9e00390.el7sat.noarch
* foreman-vmware-1.15.0-0.develop.201703271956git40dd32b.el7sat.noarch
* katello-3.4.0-1.nightly.el7sat.noarch
* katello-ca-consumer-sat-r220-02.lab.eng.rdu2.redhat.com-1.0-1.noarch
* katello-certs-tools-2.4.0-1.el7sat.noarch
* katello-client-bootstrap-1.3.0-1.el7sat.noarch
* katello-common-3.4.0-1.nightly.el7sat.noarch
* katello-debug-3.4.0-1.nightly.el7sat.noarch
* katello-default-ca-1.0-1.noarch
* katello-installer-base-3.5.0-1.nightly.201703312206git730de81.el7sat.noarch
* katello-selinux-3.0.2-1.el7sat.noarch
* katello-server-ca-1.0-1.noarch
* katello-service-3.4.0-1.nightly.el7sat.noarch
* pulp-client-1.0-1.noarch
* pulp-docker-plugins-2.3.0-1.el7sat.noarch
* pulp-katello-1.0.2-1.el7sat.noarch
* pulp-ostree-plugins-1.2.0-1.el7sat.noarch
* pulp-puppet-plugins-2.12.1-1.el7sat.noarch
* pulp-puppet-tools-2.12.1-1.el7sat.noarch
* pulp-rpm-plugins-2.12.1-1.el7sat.noarch
* pulp-selinux-2.12.1-1.el7sat.noarch
* pulp-server-2.12.1-1.el7sat.noarch
* satellite-6.3.0-11.1.beta.el7sat.noarch
* satellite-cli-6.3.0-11.1.beta.el7sat.noarch
* satellite-installer-6.3.0-6.el7sat.noarch
* tfm-rubygem-foreman_theme_satellite-1.0.3-1.el7sat.noarch
Comment 3 Brad Buckingham 2017-04-20 23:34:04 UTC 
Created redmine issue http://projects.theforeman.org/issues/19338 from this bug
Comment 4 Brad Buckingham 2017-05-11 15:22:23 UTC 
Upstream Katello PR: https://github.com/Katello/katello/pull/6784
Comment 5 Satellite Program 2017-05-16 02:11:07 UTC 
Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/19338 has been resolved.
Comment 6 Justin Sherrill 2017-08-02 16:04:23 UTC 
verified in 6.3.0 snap 9.0:

Puppet classes showed up after publish of a content view with a module
Comment 7 Bryan Kearney 2018-02-21 16:31:53 UTC 
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-2018:0336
Note You need to log in before you can comment on or make changes to this bug.