Created attachment 1489063 [details]
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
Steps to Reproduce:
1. Run 'hammer host create' command without specifying --interface parameter
[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
Host created successfully
This only happens with APIv4.
This is not hammer related, when tou see 500 in production.log, it's server side bug. When you specify it correctly, does it work as expected?
I wasn't able to reproduce this in WebUI.
In Hammer, it works with correct specification.
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.
I think this is NOT a 6.4 blocker as APIv4 seems to work in other cases and the feature is marked as experimental.
Created redmine issue https://projects.theforeman.org/issues/25276 from this bug
Upstream bug assigned to firstname.lastname@example.org
Upstream bug assigned to email@example.com
Moving this bug to POST for triage into Satellite 6 since the upstream issue https://projects.theforeman.org/issues/25276 has been resolved.
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.