Bug 1201190
Summary: | Puppet classes not showing Host Group Membership when used through Config Groups | ||||||
---|---|---|---|---|---|---|---|
Product: | Red Hat Satellite | Reporter: | Tomer Brisker <tbrisker> | ||||
Component: | WebUI | Assignee: | Tomer Brisker <tbrisker> | ||||
Status: | CLOSED CURRENTRELEASE | QA Contact: | Tazim Kolhar <tkolhar> | ||||
Severity: | medium | Docs Contact: | |||||
Priority: | unspecified | ||||||
Version: | 6.1.0 | CC: | bbuckingham, bkearney, cwelton, tbrisker, tkolhar | ||||
Target Milestone: | Unspecified | Keywords: | Triaged | ||||
Target Release: | Unused | ||||||
Hardware: | Unspecified | ||||||
OS: | Unspecified | ||||||
URL: | http://projects.theforeman.org/issues/5723 | ||||||
Whiteboard: | |||||||
Fixed In Version: | Doc Type: | Bug Fix | |||||
Doc Text: | Story Points: | --- | |||||
Clone Of: | Environment: | ||||||
Last Closed: | 2015-08-12 13:59:07 UTC | Type: | --- | ||||
Regression: | --- | Mount Type: | --- | ||||
Documentation: | --- | CRM: | |||||
Verified Versions: | Category: | --- | |||||
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
Cloudforms Team: | --- | Target Upstream Version: | |||||
Embargoed: | |||||||
Attachments: |
|
Description
Tomer Brisker
2015-03-12 09:40:54 UTC
Created from redmine issue http://projects.theforeman.org/issues/5723 hi please provide verification steps thanks Verification steps: 1. Create puppetclass, config group and host group. 2. Assign puppetclass to config group. 3. Assign config group to host group. Steps 2&3 should be checked both in order and in reverse order. Expected result: puppetclass list view shows host group in the "host groups" column. VERIFIED: # rpm -qa | grep foreman puppet-foreman_scap_client-0.3.3-8.el7sat.noarch ruby193-rubygem-foreman_docker-1.2.0.10-1.el7sat.noarch ruby193-rubygem-foreman-tasks-0.6.12.4-1.el7sat.noarch rubygem-hammer_cli_foreman_discovery-0.0.1.8-1.el7sat.noarch foreman-libvirt-1.7.2.18-1.el7sat.noarch ruby193-rubygem-foreman_bootdisk-4.0.2.12-1.el7sat.noarch foreman-compute-1.7.2.18-1.el7sat.noarch foreman-ovirt-1.7.2.18-1.el7sat.noarch ruby193-rubygem-foreman_discovery-2.0.0.12-1.el7sat.noarch rubygem-hammer_cli_foreman_tasks-0.0.3.4-1.el7sat.noarch foreman-debug-1.7.2.18-1.el7sat.noarch foreman-postgresql-1.7.2.18-1.el7sat.noarch qe-sat6-rhel71.usersys.redhat.com-foreman-client-1.0-1.noarch qe-sat6-rhel71.usersys.redhat.com-foreman-proxy-1.0-1.noarch ruby193-rubygem-foreman_gutterball-0.0.1.9-1.el7sat.noarch foreman-1.7.2.18-1.el7sat.noarch foreman-gce-1.7.2.18-1.el7sat.noarch ruby193-rubygem-foreman_hooks-0.3.7-2.el7sat.noarch rubygem-hammer_cli_foreman-0.1.4.10-1.el7sat.noarch foreman-selinux-1.7.2.13-1.el7sat.noarch foreman-vmware-1.7.2.18-1.el7sat.noarch rubygem-hammer_cli_foreman_bootdisk-0.1.2.6-1.el7sat.noarch foreman-proxy-1.7.2.4-1.el7sat.noarch qe-sat6-rhel71.usersys.redhat.com-foreman-proxy-client-1.0-1.noarch ruby193-rubygem-foreman-redhat_access-0.1.0-1.el7sat.noarch steps: 1. Create puppetclass, config group and host group. 2. Assign puppetclass to config group. 3. Assign config group to host group. Steps 2&3 should be checked both in order and in reverse order. Expected result: puppetclass list view shows host group in the "host groups" column. screenshot attached Created attachment 1021727 [details]
host group added to puppet classes
This bug is slated to be released with Satellite 6.1. This bug was fixed in version 6.1.1 of Satellite which was released on 12 August, 2015. |