Bug 1317360

Summary:	[RFE] “Terminate" on Horizon UI is Confusing
Product:	Red Hat OpenStack	Reporter:	James Biao <jbiao>
Component:	python-django-horizon	Assignee:	Matthias Runge <mrunge>
Status:	CLOSED NOTABUG	QA Contact:	Ido Ovadia <iovadia>
Severity:	medium	Docs Contact:
Priority:	unspecified
Version:	7.0 (Kilo)	CC:	aortega, athomas, mrunge, yeylon
Target Milestone:	---	Keywords:	FutureFeature
Target Release:	8.0 (Liberty)
Hardware:	Unspecified
OS:	Linux
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2016-03-14 06:59:41 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:

Description James Biao 2016-03-14 05:57:34 UTC

Description of problem:

In one of my support case, customer thought "terminate" is to shutdown the instances. As a result they lost 100+ instances.

Moving "terminate" to the "actions" dropdown list and provide a more clear warning message while "terminate" might help customer save the instances before it is too late.

Upstream also discussed this but seen as "by design"
https://bugs.launchpad.net/horizon/+bug/1408185



Version-Release number of selected component (if apfplicable):


How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 2 Matthias Runge 2016-03-14 06:59:41 UTC

Horizon prints out a clear warning, that this action can not be undone.

Terminate is already on actions list. This has been discussed upstream already, and upstream decided not to change this.