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.
Description of problem:
The customer would like to be able to run a hammer command and add an OpenSCAP Capsule and/or a Compute Profile to a Host Group. These parameters are not currently available.
Version-Release number of selected component (if applicable):
How reproducible: 100%
Steps to Reproduce:
1. Create a host group (or use a created one)
2. Attempt to add either an OpenSCAP Capsule or a Compute Profile via hammer
3.
Actual results:
Not currently available
Expected results:
Addition of either OpenSCAP Capsule and/or Compute Profile to Host Group
Additional info:
n/a
The openscap part has been implemented by BZ 1561796, compute profile commands have been merged in upstream in February but I didn't see the hostgroup assignment in the PR. Shira, do you know if assigning compute profile to hostgroup is now possible via hammer?
I'm updating the BZ to reflect only the potentially missing part.
Comment 14Lukáš Hellebrandt
2019-11-26 14:54:01 UTC
This seems to work in Hammer: `hammer hostgroup {create,update} --help` contains arguments --compute-profile and --compute-profile-id. Then, a newly created machine, upon selecting its hostgroup, indeed has parameters as specified in the compute profile. However:
1) I wasn't able to track which upstream issue introduced these changes
2) It is possible to select any compute profile. In WebUI, it is only possible to select a compute profile that has attributes for at least one compute resource (i.e. is not shown as "unspecified" when open through Infrastructure -> Compute Profiles -> <compute_profile>). Furthermore, when selecting a compute profile through Hammer that would be hidden in WebUI, that compute profile is then shown in WebUI when editing that (and only that!) hostgroup.
3) Note that it is possible to set compute profile through Hammer even without setting compute resource. During host creation in WebUI, the fields for values set in compute profile are only shown when a compute resource is selected. On the the other side, when editing a hostgroup in WebUI, it is also possible to set a compute profile without setting compute resource so this is probably expected behavior.
I consider 2) a minor bug but am open to be proven otherwise.
Comment 15Lukáš Hellebrandt
2019-11-27 11:00:37 UTC
After discussion with Shira, I decided to verify this BZ and report a separate BZ for issue 2) because it is an issue in API (which is used by Hammer and which also allows to select "unspecified" compute profile). Verified on Sat 6.7 snap 2.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.
https://access.redhat.com/errata/RHSA-2020:1454