ec2-api

Volume create time format is not as per the AWS create time

Bug #1318588 reported by Swami Reddy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
OpenStack Compute (nova)
Opinion
Undecided
Unassigned
ec2-api
Confirmed
Low
Unassigned

Bug Description

With openstack, the volume creation time is '<createTime>2014-05-12T10:08:22.000000</createTime>'
But with AWS, create volume time shows as :'<createTime>2014-05-12T10:06:41.885Z</createTime>'

For microseconds, 3 digits are extra and time zone is missing. This need to be fixed to sync-up with AWS create volume time.
Doesn't look like a big issue though, but nevertheless shouldn't happen.

Tags: ec2
Tracy Jones (tjones-i)
tags: added: compute
Joe Gordon (jogo)
tags: added: ec2
removed: compute
Revision history for this message
Sean Dague (sdague) wrote :

are you sure this is still an issue, it appears addressed in the code

Changed in nova:
status: New → Incomplete
Revision history for this message
Swami Reddy (swamireddy) wrote :

Hi Sean Dague - The reported issue not addressed yet.
As checked it and the volume create time shows as below:
==
 <createTime>2014-09-12T06:33:53.641293</createTime>
===
Still, 3 digits of micros seconds are extra and time zone information missing.

NOTE: I cloud see instead of "000000" in micro seconds, now its show correct values.

Revision history for this message
Sean Dague (sdague) wrote :

Suggest this gets addressed in out of tree ec2

Changed in nova:
status: Incomplete → Opinion
Andrey Pavlov (apavlov-e)
Changed in ec2-api:
status: New → Confirmed
importance: Undecided → Low
Revision history for this message
Swami Reddy (swamireddy) wrote :

Can we target this bug fix for L release?

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.