Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1105674
See https://bugzilla.redhat.com/show_bug.cgi?id=1105671.

I mis-configrued the ami for my compute resource. When I attempted to create a new host I briefly saw an error, but then the screen was redirected. The only way to debug the issue was to look at the logs. I would have expected an error message on the screen which gave me the error condition.

The actual logs are attached. Per Greg, the error message was

"Fog error: The image id '[ami-e08efbd0]' does  not exist"

foreman-compute-1.6.0.13-1.el6sat.noarch
dhcp137-115.rdu.redhat.com-foreman-proxy-1.0-1.noarch
foreman-ovirt-1.6.0.13-1.el6sat.noarch
rubygem-hammer_cli_foreman_tasks-0.0.3-2.el6sat.noarch
foreman-gce-1.6.0.13-1.el6sat.noarch
ruby193-rubygem-foreman_hooks-0.3.5-2.el6sat.noarch
ruby193-rubygem-foreman_bootdisk-2.0.6-1.1.el6sat.noarch
rubygem-hammer_cli_foreman-0.1.1-5.el6sat.noarch
foreman-vmware-1.6.0.13-1.el6sat.noarch
ruby193-rubygem-foreman_discovery-1.3.0-0.1.rc2.el6sat.noarch
foreman-postgresql-1.6.0.13-1.el6sat.noarch
foreman-selinux-1.6.0-3.el6sat.noarch
dhcp137-115.rdu.redhat.com-foreman-client-1.0-1.noarch
ruby193-rubygem-foreman-redhat_access-0.0.4-1.el6sat.noarch
foreman-libvirt-1.6.0.13-1.el6sat.noarch
foreman-proxy-1.6.0.6-1.el6sat.noarch
foreman-1.6.0.13-1.el6sat.noarch
ruby193-rubygem-foreman-tasks-0.5.7-2.el6sat.noarch