Created attachment 1537095 [details]
Description of problem:
When using APIv4, host creatin always fails with "Failed to create a compute rhev4 (RHV) instance ramon-rozycki.testdom: Ovirt client returned an error: undefined method `href' for nil:NilClass"
Version-Release number of selected component (if applicable):
Reproduced on Sat 6.5 snap 15. It worked in some previous snap.
Steps to Reproduce:
1. Have a RHEV, add it as a CR to Satellite using APIv4
2. Hosts -> Create host -> fill -> submit
"Failed to create a compute rhev4 (RHV) instance ramon-rozycki.testdom: Ovirt client returned an error: undefined method `href' for nil:NilClass"
Successfully created Host and VM
Created redmine issue https://projects.theforeman.org/issues/26168 from this bug
This is caused by the same issue as: https://bugzilla.redhat.com/show_bug.cgi?id=1634760 so they will be fixed together.
I've just reproduced this bug with a Sat 6.4.1 instance. That means it's probably NOT a regression (still might be 6.4.1 x 6.4, not likely though).
Ori discovered this only happened with some RHEV instances, and not with some others (which initially made me think this was a regression). The instances on which the bug is reproducible may be somehow broken but it can also be caused by some valid state, we don't know yet. However, even if those instances were broken, the bug is still valid because "undefined method" is not an acceptable response to an invalid RHEV instance state.
I agree and the bug I mentioned in Comment 6 will fix this. The fix was merged upstream but needs a new version of fog-ovirt.
Due to the dependency bump needed, the fact that the connected bug was not aligned to 6.5 and that it is not a regression, could this bug be moved out of 6.5?
Based on comment #8, I'm moving this to POST, since https://bugzilla.redhat.com/show_bug.cgi?id=1634760 is in POST.
Verified with Sat 6.7 snap 14, using reproducer from OP.
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.