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.

Description of problem:
CU is having a number of host groups and he is applying the SCAP policy to the hostgroups but the clients attached to the satellite hostgroup are not inheriting the scap policy


Version-Release number of selected component (if applicable):
6.2.10

How reproducible:
100% always

Steps to Reproduce:

1. Create hostgroups as shown below
parent
parent/child1    <-- policy is selected for this host group
parent/child1/child2
parent/child1/child2/child3    <--- hosts are installed in this hostgroup,but don't run openscap policy from two layers up.

2. Assign a SCAP policy to hostgroup parent/child1

3. attach the host to parent/child1/child2/child3

Actual results:

Clients attached to parent/child1/child2/child3 are not scanned against the scap policy that is attached to parent/child1


Expected results:
Clients attached to parent/child1/child2/child3 should inherit the policy and should be scanned against the scap policy that is attached to parent/child1

Thank you for reporting this bug. We are aware of it already and track it in 1298903, so I will close this as a duplicate. Feel free to reopen if I misunderstood and this is a different issue.

*** This bug has been marked as a duplicate of bug 1298903 ***