Bug 1121848

Summary:	[RFE][horizon]: On instance detail page add host server's name
Product:	Red Hat OpenStack	Reporter:	RHOS Integration <rhos-integ>
Component:	python-django-horizon	Assignee:	Matthias Runge <mrunge>
Status:	CLOSED ERRATA	QA Contact:	Ido Ovadia <iovadia>
Severity:	low	Docs Contact:
Priority:	medium
Version:	unspecified	CC:	aortega, athomas, markmc, mlopes, mrunge, nbarcet, yeylon
Target Milestone:	Upstream M1	Keywords:	FutureFeature, OtherQA
Target Release:	7.0 (Kilo)
Hardware:	Unspecified
OS:	Unspecified
URL:	https://blueprints.launchpad.net/horizon/+spec/instance-details-add-host-server
Whiteboard:	upstream_milestone_kilo-1 upstream_definition_approved upstream_status_implemented
Fixed In Version:	python-django-horizon-2015.1.0-9.el7ost	Doc Type:	Enhancement
Doc Text:	In OpenStack Dashboard, the instance detail page now displays the host node. This data is intended to assist when diagnosing issues.	Story Points:	---
Clone Of:		Environment:
Last Closed:	2015-08-05 13:13:10 UTC	Type:	---
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description RHOS Integration 2014-07-22 04:10:43 UTC

Cloned from launchpad blueprint https://blueprints.launchpad.net/horizon/+spec/instance-details-add-host-server.

Description:

When using #nova show <Instance>  we get lots of details about an instance including : OS-EXT-SRV-ATTR:host  |  puma31.... name of server running the instance.  

Clicking on an instance's details from Horizion host server's name is missing and should be added. Reason being in case of troubleshooting an instance having this info easily accessible here could be helpful in determining which host needs to be checked if it's a host related problem.    

Specification URL (additional information):

None

Comment 5 Ido Ovadia 2015-07-22 13:23:58 UTC

Verified
========
python-django-horizon-2015.1.0-10.el7ost.noarch

Comment 7 errata-xmlrpc 2015-08-05 13:13:10 UTC

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/RHEA-2015:1548