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.

Bug 1207616

Summary: Creating a 'Full Host' type boot disk image raises 500 ISE when host is not set in build mode
Product: Red Hat Satellite Reporter: Sachin Ghai <sghai>
Component: Bootdisk PluginAssignee: Lukas Zapletal <lzap>
Status: CLOSED WONTFIX QA Contact: Katello QA List <katello-qa-list>
Severity: low Docs Contact:
Priority: unspecified    
Version: 6.1.0CC: bkearney, lzap
Target Milestone: UnspecifiedKeywords: Triaged
Target Release: Unused   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2017-01-05 14:03:17 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
Oops, we're sorry but something went wrong on selecting 'Full host' type image none

Description Sachin Ghai 2015-03-31 10:18:49 UTC
Created attachment 1008925 [details]
Oops, we're sorry but something went wrong on selecting 'Full host' type image

Description of problem:
I was trying to test boot disk image feature. But when I selected "Full Host image" from BootDisk dropdown under the host details page, I got :

--
Oops, we're sorry but something went wrong
ERF42-2893 [Foreman::Exception]: Host is not in build mode, so the template cannot be rendered
--

and 500 ISE in production.log:

--
2015-03-31 15:43:05 [I] Processing by ForemanBootdisk::DisksController#full_host as HTML
2015-03-31 15:43:05 [I]   Parameters: {"id"=>"capsuleboothostimage.lab.eng.pnq.redhat.com"}
2015-03-31 15:43:05 [W] Operation FAILED: ERF42-2893 [Foreman::Exception]: Host is not in build mode, so the template cannot be rendered
2015-03-31 15:43:05 [I]   Rendered common/500.html.erb within layouts/application (5.3ms)
2015-03-31 15:43:05 [I]   Rendered layouts/base.html.erb (1.5ms)
2015-03-31 15:43:05 [I] Completed 500 Internal Server Error in 31ms (Views: 9.4ms | ActiveRecord: 3.5ms)
---

Though the error thrown is correct but it should not be raised with:

Oops, we're sorry but something went wrong

we should convert is it to error message in red box.


Version-Release number of selected component (if applicable):
Sat6.1 beta snap8
Satellite-6.1.0-RHEL-7-20150324.0

How reproducible:
always

Steps to Reproduce:
1.
2.
3.

Actual results:
--
Oops, we're sorry but something went wrong
ERF42-2893 [Foreman::Exception]: Host is not in build mode, so the template cannot be rendered
--


Expected results:
In case host is not set in build mode, UI should raise an error message without the "Oops, we're sorry but something went wrong" window and logs shouldn't contain 500 ISE.

Additional info:

Comment 4 Lukas Zapletal 2015-04-01 13:21:33 UTC
Trivial errors should have been reported upstream only.

Comment 5 Bryan Kearney 2017-01-05 14:03:17 UTC
This is an older bug which I do not envision being fixed in the near term. I am closing this out. If you belive doing so is an issue, please feel free to re-open and provide additional business information. Thank you!