Bug 866577 - [RFE] vsphere instance reboots should do proper os shutdown
Summary: [RFE] vsphere instance reboots should do proper os shutdown
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: CloudForms Cloud Engine
Classification: Retired
Component: deltacloud-core
Version: 1.1.0
Hardware: Unspecified
OS: Unspecified
high
medium
Target Milestone: rc
Assignee: Michal Fojtik
QA Contact: Dave Johnson
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2012-10-15 16:21 UTC by Dave Johnson
Modified: 2012-10-26 22:07 UTC (History)
3 users (show)

Fixed In Version:
Clone Of:
Environment:
Last Closed: 2012-10-26 22:07:38 UTC
Embargoed:


Attachments (Terms of Use)

Description Dave Johnson 2012-10-15 16:21:13 UTC
Description of problem:
=================================
So when a vsphere instance has the vm tools (agent) installed, cloud engine can restart the instance.  While testing this out, I noticed that the reboot is actually a hard reset... it seems vsphere has a reboot guest os option and curious if that would be a better api call to use than the reset one


Version-Release number of selected component (if applicable):
====================================================================
aeolus-conductor-0.13.18-1.el6cf.noarch
deltacloud-core-0.5.0-10.el6_2.noarch
deltacloud-core-vsphere-0.5.0-10.el6_2.noarch

Comment 2 Tomas Hrcka 2012-10-25 08:07:37 UTC
Deltacloud api invoke vsphere reboot action, if you look at vsphere client after clicking reboot in conductor it does schedule vsphere-vm-reboot action. If you are using console from vsphere-client there you will not see any shutting down service messages when wm is rebooting, so it may be look like reset but its not true we are invoking proper reboot on vsphere.

Comment 3 Dave Johnson 2012-10-26 22:07:38 UTC
While ssh'd into a instance, reboot action from conductor causes "The system is going down for reboot NOW!" to be printed out so it appears this is working correctly.


Note You need to log in before you can comment on or make changes to this bug.