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 1920667

Summary: [RFE] Better tools to manage Host System Purpose in Bulk
Product: Red Hat Satellite Reporter: patalber
Component: HostsAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED DUPLICATE QA Contact: tstrych
Severity: medium Docs Contact:
Priority: unspecified    
Version: 6.8.0CC: inecas
Target Milestone: UnspecifiedKeywords: FutureFeature
Target Release: Unused   
Hardware: All   
OS: All   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2021-01-27 14:39:54 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 patalber 2021-01-26 20:17:56 UTC
1. Proposed Title of RFE:
Better Tools for Managing Host System Purpose in Bulk

2. What is the nature and description of the request?

The customer has 1000+ hosts that need their service level manipulated in the GUI, and the only tool that appears to be available is within each individual host page. There is not a mechanic to do this via the 'Select Action' button that I have found. There is a way to do this in bulk via Hammer:

# hammer host update --service-level

This can be looped to perform such an update in bulk. There should be a similar mechanic available via the GUI.

3. Why do you need this?

1000+ hosts would take a long time to perform this task manually via the GUI. Since RHEL8 uses service level as part of System Purpose, this feels like a good time to manipulate System Purpose in bulk like other aspects of hosts in satellite (subscriptions, repo sets, release version, etc).

4. How would you like to achieve this?

Using similar mechanics that currently allow manipulation of attached entitlements, enabled repo sets, set release versions, etc.

5. For each functional requirement listed, specify how Red Hat and your organization can test to confirm the requirement is successfully implemented.

Take a number of sample hosts (say, 150) and use the engineered mechanic in the GUI to perform a simple test of System Purpose manipulation.

6. Is there already an existing RFE upstream?

No

7. Do you have any specific timeline dependencies and which release would they like to target?

No

8. List any affected packages or components

Katello (I believe)

9. Would you be able to assist in testing this functionality if implemented?

Possibly

Comment 1 Brad Buckingham 2021-01-27 14:39:54 UTC
This appears to be a duplicate of bug 1894159; therefore, I am going to close this as a duplicate.

With that bugzilla, the Satellite UI is being enhanced to support a bulk action for setting System Purpose attributes on multiple hosts.

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