Note: This bug is displayed in read-only format because the product is no longer active in Red Hat Bugzilla.

Bug 855828

Summary: [RFE]-Should show the Event time in local time zone
Product: [Retired] CloudForms Cloud Engine Reporter: Rehana <redakkan>
Component: aeolus-conductorAssignee: Angus Thomas <athomas>
Status: CLOSED EOL QA Contact: Rehana <aeolus-qa-list>
Severity: low Docs Contact:
Priority: low    
Version: 1.1.0CC: dajohnso, morazi, sshveta
Target Milestone: rcKeywords: FutureFeature
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Enhancement
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2020-03-27 17:58:27 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:
Attachments:
Description Flags
time none

Description Rehana 2012-09-10 10:44:58 UTC
Created attachment 611393 [details]
time

Description of problem:


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


How reproducible:
100%

Steps to Reproduce:
1.Ligin to conductor
2.Launch few instance
3.Go to History /Logs of the instance
  
Actual results:
Observed that the logs/event were displayed against the server time which is EDT(PFA)

Expected results:
It will better if the event can record the local time (timezone from where the URL is accessed) instead of showing the server time

Additional info:
rpm -qa | grep aeolus
rubygem-aeolus-cli-0.7.0-0.20120909230025git8a46b3f.fc16.noarch
rubygem-aeolus-image-0.6.0-0.20120909230031git902c81c.fc16.noarch
aeolus-conductor-0.13.0-0.20120910030008gitb478e0c.fc16.noarch
aeolus-conductor-daemons-0.13.0-0.20120910030008gitb478e0c.fc16.noarch
aeolus-all-0.13.0-0.20120910030008gitb478e0c.fc16.noarch
aeolus-conductor-doc-0.13.0-0.20120910030008gitb478e0c.fc16.noarch
aeolus-configure-2.8.0-0.20120909230024gitb24d837.fc16.noarch

Comment 1 Rehana 2012-09-10 10:48:31 UTC
typo

steps

Steps to Reproduce:
1.Login to conductor
2.Launch few instance
3.Go to History /Logs of the instance

Comment 2 Rehana 2012-09-10 11:00:20 UTC
Updating the expected result, observed that on conductor it displayed the GMT time not server time

Expected results:
It will better if the event can record the local time (timezone from where the URL is accessed) instead of showing GMT time.

Comment 4 Shveta 2012-11-12 19:55:59 UTC
The Logs timestamp does not even show server time zone.
On Server :

[root@hp-magnycours-01 ~]# date
Mon Nov 12 14:53:21 EST 2012


Logs in UI shows :  12-Nov-2012 19:29:37