Bug 890161

Summary: Missing option to start an instance
Product: Red Hat OpenStack Reporter: Ofer Blaut <oblaut>
Component: python-django-horizonAssignee: Julie Pichon <jpichon>
Status: CLOSED ERRATA QA Contact: Nir Magnezi <nmagnezi>
Severity: low Docs Contact:
Priority: medium    
Version: 2.0 (Folsom)CC: athomas, jpichon, mlopes
Target Milestone: Upstream M2Keywords: Triaged
Target Release: 4.0   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: python-django-horizon-2013.2-0.12b3.el6ost Doc Type: Enhancement
Doc Text:
Instances can now be started from the Instances list page. Previously, there was no clear method to start an instance in a shutdown state without using workarounds such as 'Reboot'. This enhancement addresses this by adding a new 'Start' option in the Instances list page for shutdown instances.
Story Points: ---
Clone Of: Environment:
Last Closed: 2013-12-19 18:53:58 EST Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:

Description Ofer Blaut 2012-12-25 07:13:15 EST
Description of problem:

Nova cli support start of instance ( nova start )
This option is not avilable in horizon.
After node reboot all instances are in power off state and the only option is restart 

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


How reproducible:


Steps to Reproduce:
1.reboot node with running instance
2.look for option to start instance 
3.
  
Actual results:

No option to start instance only reboot it

Expected results:


Additional info:
Comment 4 Nir Magnezi 2013-11-12 02:43:54 EST
Tested NVR: python-django-horizon-2013.2-3.el6ost.noarch

Verification Steps:
===================

1. Start an instance.
2. Reboot the compute node.
3. Verify that at Horizon Instances page, the instance status is SHUTDOWN
4. Verify that "Start Instance" option is available, Click it.

Result:
=======
Instance successfully started.
Comment 7 errata-xmlrpc 2013-12-19 18:53:58 EST
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.

http://rhn.redhat.com/errata/RHEA-2013-1859.html