Bug 783378

Summary: History of restarted/rebooted instances is not maintained in instance detail events.
Product: [Retired] CloudForms Cloud Engine Reporter: Aziza Karol <akarol>
Component: aeolus-conductorAssignee: Jan Provaznik <jprovazn>
Status: CLOSED CURRENTRELEASE QA Contact: wes hayutin <whayutin>
Severity: medium Docs Contact:
Priority: unspecified    
Version: 1.0.0CC: akarol, deltacloud-maint, hbrock, jprovazn, ssachdev
Target Milestone: rc   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2012-12-13 19:49:04 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
event details
none
history none

Description Aziza Karol 2012-01-20 07:39:28 UTC 
Description of problem:


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


How reproducible:


Steps to Reproduce:
I rebooted and restarted a mock instance.
I see that the history for restart and reboot instance is not maintained in the instance detail events.

see attached screenshot.
Also in the screenshot if you see the latest action is displayed at the top.
The stopped event is displayed first and the created event it displayed at the last.I think it should be vice-versa. 


Expected results:
History of restarted/rebooted instances should be also maintained in instance detail events

Additional info:rpm -qa | grep aeolus
rubygem-aeolus-image-0.3.0-3.el6.noarch
rubygem-aeolus-cli-0.3.0-4.el6.noarch
aeolus-conductor-doc-0.8.0-8.el6.noarch
aeolus-configure-2.5.0-5.el6.noarch
aeolus-conductor-daemons-0.8.0-8.el6.noarch
aeolus-all-0.8.0-8.el6.noarch
aeolus-conductor-0.8.0-8.el6.noarch
aeolus-conductor-devel-0.8.0-8.el6.noarch
Comment 1 Aziza Karol 2012-01-20 07:40:30 UTC 
Created attachment 556464 [details]
event details
Comment 2 wes hayutin 2012-01-25 16:36:12 UTC 
I need more details here.. does the history stop after a reboot?
Comment 3 Jan Provaznik 2012-02-08 12:23:58 UTC 
patch sent: https://fedorahosted.org/pipermail/aeolus-devel/2012-February/008715.html

patch doesn't change order of events (stays descending), but now there is time displayed. I remember there was a request from QA long time ago if order could be descending - reason for this is that if the list of events is long, user had to scroll at the end/jump to last page (list is paginated).

Should be ordering really changed?
Comment 4 Jan Provaznik 2012-02-08 15:42:26 UTC 
fixed in commit 2408968b84cb611b1021c317c085d472bfe17376
Comment 5 Shveta 2012-02-13 15:45:08 UTC 
Created attachment 561585 [details]
history
Comment 6 Shveta 2012-02-13 15:46:03 UTC 
history displayed properly

rpm -qa|grep aeolus
aeolus-conductor-0.8.0-25.el6.noarch
aeolus-conductor-doc-0.8.0-25.el6.noarch
rubygem-aeolus-cli-0.3.0-8.el6.noarch
aeolus-conductor-daemons-0.8.0-25.el6.noarch
aeolus-configure-2.5.0-12.el6.noarch
aeolus-all-0.8.0-25.el6.noarch
rubygem-aeolus-image-0.3.0-7.el6.noarch