Hide Forgot
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
Created attachment 556464 [details] event details
I need more details here.. does the history stop after a reboot?
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?
fixed in commit 2408968b84cb611b1021c317c085d472bfe17376
Created attachment 561585 [details] history
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