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:
In satellite 6, there is not hammer command to enable/disable notifications
for a particular host.
This feature is available in GUI:
1) Hosts > All Hosts > Tick host >Select Action > Disable Notification
2) Hosts > All Hosts > Tick host >Select Action > Enable Notification
Version-Release number of selected component (if applicable):
Satellite 6.2.8
How reproducible:
#hammer host update --help
#hammer host create --help
Actual results:
No option available to enable/disable notifications for a host via hammer cli.
Expected results:
#hammer host update --name <hostname> --notifications <enable/disable>
# hammer host update --help
Usage:
hammer host update [OPTIONS]
Options:
--id ID
--enabled ENABLED One of true/false, yes/no, 1/0.
# hammer host list
---|------------------------------------------|------------------|------------|---------------|------------------
ID | NAME | OPERATING SYSTEM | HOST GROUP | IP | MAC
---|------------------------------------------|------------------|------------|---------------|------------------
8 | xxxxx-client1 | RedHat 7.3 | | 10.xx.yyy.199 | 00:9a:3a:01:00:1x
11 | xxxxx-client2 | RedHat 7.1 | | 10.xx.yyy.122 | 00:9a:3a:01:00:3x
10 | xxxxx-client2 | RedHat 7.1 | | 10.xx.yyy.122 | 00:9a:3a:01:00:3x
1 | xxxxx-sat62 | RedHat 7.3 | | 10.xx.yyy.174 | 00:9a:3a:01:00:2x
---|------------------------------------------|------------------|------------|---------------|------------------
# hammer host update --id 8 --enabled false
Host updated
# hammer host update --id 8 --enabled true
Host updated
This work fine for one host. Need to add more details in hammer help that following option is used for enable/disable notification.
Options:
--id ID
--enabled ENABLED One of true/false, yes/no, 1/0. <<<---Used for host notification.
Hi - Since upstream issue is resolved, can we set target release or include this in next satellite release (6.2.11)? Please let us know if its achievable. Thanks.
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-2018:2927