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.
DescriptionOmkar Khatavkar
2021-07-02 15:45:52 UTC
Description of problem:
[global registration] [hammer] - hammer --remote-execution-interface false | no|0 is not working
Version-Release number of selected component (if applicable):
Satellite 6.10 Snap 7
How reproducible:
always
Steps to Reproduce:
host-registration generate-command --activation-keys RHEL8_Content_Activation_Key --packages 'mlocate vim' --force true --setup-insights 0 --remote-execution-interface false
host-registration generate-command --activation-keys RHEL8_Content_Activation_Key --packages 'mlocate vim' --force true --setup-insights 0 --remote-execution-interface no
host-registration generate-command --activation-keys RHEL8_Content_Activation_Key --packages 'mlocate vim' --force true --setup-insights 0 --remote-execution-interface 0
Actual results:
registion leads to an error
ERROR: not_found
Interface with the 'false' identifier was specified as a remote execution interface, however, the interface was not found on the host. If the interface exists, it needs to be created in Foreman during the registration.
Expected results:
registration shouls not get any error and rex should nto be applied
Additional info:
from UI this is working as expected