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
2019-12-05 10:25:38 UTC
Description of problem:
When creating a host on RHEV using APIv3, I get:
"Failed to create a compute testrhev3 (RHV) instance <FQDN>: Ovirt client returned an error: undefined method `text' for nil:NilClass"
This is regression.
Version-Release number of selected component (if applicable):
Sat 6.7 snap 4.
How reproducible:
Deterministic
Steps to Reproduce:
1. Have a RHEV CR using APIv3 and other entities necessary to create a host
2. Try to create a host
Actual results:
Upon submitting the host creation form, I get the mentioned error and the host is not created
Expected results:
Host created successfully (or APIv3 suport removed?)
Comment 5Lukáš Hellebrandt
2019-12-06 09:11:12 UTC
Created attachment 1642585[details]
foreman-tail.log
There's no traceback in production.log. Attaching the log anyway.
I wasn't able to reproduce upstream.
Could I get the details of the RHV you are using or detailed steps on what to fill in for the host?
Maybe one of these differences is the cause.
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