Bug #19338
closedCV publishing with puppet module does not add puppet class
Description
Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1441781
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
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.
- 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
fixes #19338 - puppet classes not imported during cv publish
After 5f606e11cf39719bf62f8b1f3396861b32387905 merged into foreman
publishing a content view containing puppet modules is no longer
importing the puppet classes. In order to address it, we'll
'keep' the current user on the action. Another alternative is
to use 'unscoped' queries; however, there are multiple foreman
resources needed to support the flow and this will address them all.