Bug #11779
closedKatello is not creating puppet environments for composite content views
Description
Description of problem:
Katello is not creating puppet environment for composite content views.
No matter if they contains or not any CV with puppet modules.
Steps to Reproduce:
1. Create repository X;
2. Add puppet module to X;
3. Create content view A;
4. Include repository X to content view A;
5. Publish content view A to library;
6. Create composite content view B;
7. Include content view A to composite content view B;
8. Publish content view B to library;
9. List puppet environments.
Actual results:
Puppet environments contains default production and KT_orgname_Library_A_1.
Expected results:
Puppet environments contains default production, KT_orgname_Library_A_1 and KT_orgname_Library_B_2.
Updated by Vladimir Stackov over 9 years ago
# rpm -qa | grep -iP 'katello|foreman' rubygem-hammer_cli_katello-0.0.17-2.el7.noarch ruby193-rubygem-puppetdb_foreman-0.1.2-1.el7.noarch ruby193-rubygem-foreman_gutterball-0.0.1-1.201507061443gitb9974c7.git.0.64e9626.el7.noarch ruby193-rubygem-foreman_templates-2.0.0-1.el7.noarch katello-selinux-2.2.1-1.el7.noarch foreman-proxy-1.9.0-1.el7.noarch katello-installer-2.3.1-5.el7.noarch foreman-compute-1.9.0-1.el7.noarch foreman-libvirt-1.9.0-1.el7.noarch rubygem-hammer_cli_foreman_bootdisk-0.1.3-1.el7.noarch katello-server-ca-1.0-2.noarch katello-default-ca-1.0-1.noarch katello-installer-base-2.3.1-5.el7.noarch ruby193-rubygem-foreman_bootdisk-6.0.0-1.el7.noarch ruby193-rubygem-foreman-tasks-0.7.3-1.fm1_9.el7.noarch ruby193-rubygem-foreman_docker-1.4.1-1.fm1_9.el7.noarch ruby193-rubygem-foreman_setup-3.0.2-1.fm1_9.el7.noarch katello-certs-tools-2.3.0-4.el7.noarch rubygem-hammer_cli_foreman-0.3.0-1.el7.noarch katello-debug-2.3.0-5.el7.noarch rubygem-hammer_cli_foreman_docker-0.0.3-2.el7.noarch ruby193-rubygem-foreman_default_hostgroup-3.0.0-1.el7.noarch katello-service-2.3.0-5.el7.noarch foreman-selinux-1.9.0-1.el7.noarch foreman-1.9.0-1.el7.noarch foreman-gce-1.9.0-1.el7.noarch foreman-ovirt-1.9.0-1.el7.noarch katello-common-2.3.0-5.el7.noarch foreman-ec2-1.9.0-1.el7.noarch foreman-postgresql-1.9.0-1.el7.noarch foreman-debug-1.9.0-1.el7.noarch foreman-vmware-1.9.0-1.el7.noarch katello-2.3.0-5.el7.noarch katello-agent-2.3.1-4.el7.noarch rubygem-hammer_cli_foreman_tasks-0.0.7-1.el7.noarch pulp-katello-0.4-2.el7.noarch ruby193-rubygem-foreman_hooks-0.3.8-1.el7.noarch ruby193-rubygem-katello-2.3.0-6.el7.noarch ruby193-rubygem-foreman_discovery-4.0.0-1.fm1_9.el7.noarch
Updated by Eric Helms over 9 years ago
- Category set to Documentation
- Translation missing: en.field_release set to 78
- Triaged changed from No to Yes
Updated by Vladimir Stackov over 9 years ago
Documentation?
Am I misunderstood something and this is not a bug?
Updated by Vladimir Stackov over 9 years ago
Seems to be regression from http://projects.theforeman.org/issues/10459
Updated by The Foreman Bot over 9 years ago
- Status changed from New to Ready For Testing
- Pull request https://github.com/Katello/katello/pull/5518 added
- Pull request deleted (
)
Updated by Justin Sherrill over 9 years ago
- Assignee set to Justin Sherrill
- Priority changed from Normal to High
Updated by Justin Sherrill over 9 years ago
- Status changed from Ready For Testing to Closed
- % Done changed from 0 to 100
Applied in changeset katello|881be62205500fc14a0ceb8cd305b3cb1ce847d8.
Updated by Eric Helms almost 9 years ago
- Translation missing: en.field_release changed from 78 to 70