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-06-01 09:44:30 UTC
Description of problem:
When creating a host on RHEV using API v3 (both through WUI and CLI), the traceback appears in production.log but the machine is created regardless.
Version-Release number of selected component (if applicable):
Sat 6.4 snap 5
How reproducible:
Deterministic
Steps to Reproduce:
# hammer host create --architecture x86_64 --compute-profile-id 1 --compute-resource-id 1 --content-source-id 1 --content-view-id 1 --domain-id 2 --environment-id 1 --interface compute_network=a1f9eb04-9b92-4940-b65f-1ba87adf9cb5,mac=00:1a:4a:16:01:a8,ip=192.168.1.111,managed=true,primary=true,provision=true --ip 192.168.1.111 --lifecycle-environment-id 1 --location-id 2 --mac 00:1a:4a:16:01:a8 --name host-hammer-image-based --operatingsystem-id 1 --organization-id 1 --partition-table-id 1 --product-id 13 --provision-method image --root-password toortoor --subnet-id 1
or do the same in the WebUI
Actual results:
'Could not create the host' in Hammer, traceback in production.log (attached), but the host is created.
Expected results:
No error message, no traceback
Additional info:
Similar but different (different traceback, host NOT actually created) issue exists for API v4, will link it once I report it.
Comment 1Lukáš Hellebrandt
2018-06-01 09:54:34 UTC
It looks like the error might be related to the finish template used by the operating system that was selected for the host.
Does this happen with other compute resources? with a different template?
Comment 5Lukáš Hellebrandt
2018-06-14 09:59:03 UTC
This just happened to me with network based provisioning.
Comment 6Lukáš Hellebrandt
2018-06-14 10:05:42 UTC
Going to All Hosts -> <host> -> Templates -> View Finish Template leads to the white page with text:
"""
There was an error rendering the Satellite Kickstart Default Finish template: undefined method '#params' for Host::Managed::Jail (Host::Managed)
"""
... so this is not related to RHEV, it's a template issue.
Talking to lzap about this.
This is caused by the fact, branding plugin templates still use all (removed) macros. BZ 1572980 will fix that. I'd recommend closing as duplicate, but if you want to keep it open to reverify image based provisioning, just please keep the status in sync with that BZ.
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-2018:2927