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.
DescriptionLukáš Hellebrandt
2018-10-01 14:48:18 UTC
Created attachment 1489063[details]
production.log
Description of problem:
Running 'hammer host create ...' without --interface specification leads to error in $SUBJ
I tried it with Sat 6.3 and didn't reproduce it (got a nice message "Could not create the host: Could not find virtual machine network interface matching 192.168.1.116") => seems like regression
Version-Release number of selected component (if applicable):
Reproduced on Sat 6.4 snap 24
How reproducible:
Deterministic
Steps to Reproduce:
1. Run 'hammer host create' command without specifying --interface parameter
Actual results:
[DEBUG 2018-10-01T16:19:57 Exception] Using exception handler HammerCLIForeman::ExceptionHandler#handle_unprocessable_entity
[ERROR 2018-10-01T16:19:57 Exception] Failed to create a compute rhev4 (RHV) instance fish.example.com: Ovirt client returned an error: undefined method `href' for nil:NilClass
Could not create the host:
Failed to create a compute rhev4 (RHV) instance fish.example.com: Ovirt client returned an error: undefined method `href' for nil:NilClass
Expected results:
Host created successfully
Additional info:
Traceback attached
Comment 2Lukáš Hellebrandt
2018-10-01 14:53:53 UTC
Hammer is CLI tool that uses API provided by the server. The very same server that runs WebUI. Hammer component is only used for things on the CLI tool itself, when you see a bug on server side, please choose more specific component. In fact, try to avoid WebUI/API/Hammer components as much as possible. If it's not clear, I'm happy to explain in more details.
Comment 7Lukáš Hellebrandt
2018-10-03 09:10:41 UTC
I think this is NOT a 6.4 blocker as APIv4 seems to work in other cases and the feature is marked as experimental.
Comment 14Lukáš Hellebrandt
2020-02-13 14:03:34 UTC
Verified with Sat 6.7 snap 11 as per OP and comment 2.
When no interface specified by --interface, the command passes, using the interface from image. With PXE boot, default settings is used. This behavior is different to APIv3 which in both cases says "Could not create the host: Could not find virtual machine network interface matching <FQDN>" - reporting a followup BZ about this inconsistency.
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
Created attachment 1489063 [details] production.log Description of problem: Running 'hammer host create ...' without --interface specification leads to error in $SUBJ I tried it with Sat 6.3 and didn't reproduce it (got a nice message "Could not create the host: Could not find virtual machine network interface matching 192.168.1.116") => seems like regression Version-Release number of selected component (if applicable): Reproduced on Sat 6.4 snap 24 How reproducible: Deterministic Steps to Reproduce: 1. Run 'hammer host create' command without specifying --interface parameter Actual results: [DEBUG 2018-10-01T16:19:57 Exception] Using exception handler HammerCLIForeman::ExceptionHandler#handle_unprocessable_entity [ERROR 2018-10-01T16:19:57 Exception] Failed to create a compute rhev4 (RHV) instance fish.example.com: Ovirt client returned an error: undefined method `href' for nil:NilClass Could not create the host: Failed to create a compute rhev4 (RHV) instance fish.example.com: Ovirt client returned an error: undefined method `href' for nil:NilClass Expected results: Host created successfully Additional info: Traceback attached