Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.
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 2209971

Summary: [RFE] Select all hosts associated with child host groups by just selecting their parent host group as a target for remote execution invocation in Satellite's web UI
Product: Red Hat Satellite Reporter: momran
Component: Remote ExecutionAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED MIGRATED QA Contact: Satellite QE Team <sat-qe-bz-list>
Severity: high Docs Contact:
Priority: unspecified    
Version: 6.13.0CC: aruzicka, dsinglet, torkil
Target Milestone: UnspecifiedKeywords: FutureFeature, MigratedToJIRA, Triaged, UserExperience, WorkAround
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2024-06-06 16:14:47 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:

Description momran 2023-05-25 11:31:49 UTC
Description of problem:

When invoking a remote execution job from RH Satellite's web UI, in the 'Target hosts and inputs' step, filtering by 'Host Group', then selecting a parent host group only selects the hosts associated with this host group, but not the hosts associated with the child host groups. Child host groups need to also be selected in order for the hosts associated with them to be included as targets of the remote execution job.

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

Red Hat Satellite 6.13


How reproducible:

Always.


Steps to Reproduce:

1. Login to Red Hat Satellite's web UI.

2. Navigate to Host -> Job Templates.

3. Click on 'Run' corresponding to the job template to be used for remote execution.

4. In the second step 'Target hosts and inputs', select the 'Host groups' filter from the drop-down menu to the left, then expand the drop-down menu to the right.

5. Select a parent host group from the list.

Actual results:

Only hosts associated with the selected parent host group are included as targets for the remote execution job. Hosts associated with child host groups are not included.

Expected results:

By just selecting the parent host group, all hosts associated with it as well as with each of its child host groups are included as targets for the remote execution job.

Comment 3 Adam Ruzicka 2023-08-11 10:14:13 UTC
This is possible to accomplish even now, even though it is slightly more involved than just picking a hostgroup from a list. As an example, one can switch to search query and use "hostgroup_fullname ~ A/B/*" to match hostgroup B nested under hostgroup A and all the hostgroups nested below B

Comment 4 Eric Helms 2024-06-06 16:14:47 UTC
This BZ has been automatically migrated to the issues.redhat.com Red Hat Issue Tracker. All future work related to this report will be managed there.

Due to differences in account names between systems, some fields were not replicated.  Be sure to add yourself to Jira issue's "Watchers" field to continue receiving updates and add others to the "Need Info From" field to continue requesting information.

To find the migrated issue, look in the "Links" section for a direct link to the new issue location. The issue key will have an icon of 2 footprints next to it, and begin with "SAT-" followed by an integer.  You can also find this issue by visiting https://issues.redhat.com/issues/?jql= and searching the "Bugzilla Bug" field for this BZ's number, e.g. a search like:

"Bugzilla Bug" = 1234567

In the event you have trouble locating or viewing this issue, you can file an issue by sending mail to rh-issues. You can also visit https://access.redhat.com/articles/7032570 for general account information.