Hide Forgot
Description of problem: This is a RFE for both CloudForms and OpenStack Horizon. Not sure if we need two BZ's to address the issue since it exists in both interfaces. From the OpenStack Dashboard in Horizon, there is no differentiation between if an instance is a virtual machine running as a compute resource or if the instance is a baremetal machine deployed by Ironic. Therefore, the Console URL for the instance, regardless of type (virtual/baremetal) is statically generated using the instance ID and novnc/spice/etc as an access method. This does not work for baremetal machines as the only way to access console on them is through their management interface. This issue is propagated up into CloudForms. I don't know if the Console link in CloudForms is pulled from the Console link of Horizon or if it is generated via code within CloudForms. Either way, this is an issue that needs to be addressed in both CloudForms and the OpenStack Horizon Dashboard. Version-Release number of selected component (if applicable): All/Current How reproducible: 100% Steps to Reproduce: 1. Start up Red Hat OpenStack with Ironic running in the Overcloud 2. Deploy a baremetal instance in the Overcloud 3. Click on the Instance in CloudForms/Horizon, click on the Console URL link and it will open a window and fail Actual results: Console connectivity fails. Expected results: The Window should open to the iDrac/ILO etc using the IPMI interface of the node so the user can actually log in and get console of the baremetal node. Additional info:
Darin, is it possible to split this BZ into two, one for Horizon and one for CloudForms? I suspect different teams will be working on each.
(In reply to Tzu-Mainn Chen from comment #3) > Darin, is it possible to split this BZ into two, one for Horizon and one for > CloudForms? I suspect different teams will be working on each. Cloned as https://bugzilla.redhat.com/show_bug.cgi?id=1401079 If that is not what you were asking for, please let me know.
Looks good, thanks!
Please assess the impact of this issue and update the severity accordingly. Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#bug_severity for a reminder on each severity's definition.
Please assess the importance of this issue and update the priority accordingly. Somewhere it was missed in the bug triage process. Please refer to https://bugzilla.redhat.com/page.cgi?id=fields.html#priority for a reminder on each priority's definition. If it's something like a tracker bug where it doesn't matter, please set it to Low/Low.