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.
Created base on a discussion in https://bugzilla.redhat.com/show_bug.cgi?id=1486696
There is a need to explain the difference between two ways of adding host parameters via hammer:
hammer host update --parameters
hammer host set-parameter
The key point to be stressed is that the first method replaces existing custom parameters, while the second one appends to existing parameter set.
Document URL: https://access.redhat.com/documentation/en-us/red_hat_satellite/6.4/html/hammer_cli_guide/chap-cli_guide-managing_hosts
Section Number and Name:
Chapter 6. Managing Hosts
Describe the issue:
Basically request for addition, see above
Suggestions for improvement:
Additional information: