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.
For certain compute resources and errors, the UI may not provide enough detail to diagnose why a provision failed. The user will need to check the logs which are located at /var/log/foreman/production.log
Created attachment 902991[details]
foreman-debug output
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
Comment 7Daniel Lobato Garcia
2014-09-01 14:07:11 UTC
DEVELOPER VERIFIED: For an existent compute resource on Libvirt, I changed the URL to something unreachable, saved it. When I went to create New Host, changing 'deploy on' to that Libvirt compute resource resulted on the Fog error shown in the Virtual machine tab, no redirections whatsoever.
Tested on https://cloud-qe-10.idm.lab.bos.redhat.com
Note that editing the URL to something that is not a Compute Resource and saving it should not be possible in future versions of Sat6, but the fact that bug exists makes verifying this easier.