[Yahoo-eng-team] [Bug 1280948] Re: The DB API is inconsistent about returning sub-second resolution timestamps

2015-08-02 Thread Davanum Srinivas (DIMS)
** Changed in: nova
   Status: Confirmed = Won't Fix

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1280948

Title:
  The DB API is inconsistent about returning sub-second resolution
  timestamps

Status in ec2-api:
  Won't Fix
Status in OpenStack Compute (nova):
  Won't Fix

Bug description:
  While creating volume, the return value says that volume creation time
  is dd-mm-yyThh:mm:ss.s, but while listing volumes at a later point
  of time, it changes to dd-mm-yyThh:mm:ss.0

  Doesn't look like a big issue though, but nevertheless shouldn't
  happen. I'd say the simplest solution should be to return dd-mm-
  yyThh:mm:ss.0 at the create-time itself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ec2-api/+bug/1280948/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp


[Yahoo-eng-team] [Bug 1280948] Re: The DB API is inconsistent about returning sub-second resolution timestamps

2015-06-12 Thread Davanum Srinivas (DIMS)
** Also affects: ec2-api
   Importance: Undecided
   Status: New

-- 
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1280948

Title:
  The DB API is inconsistent about returning sub-second resolution
  timestamps

Status in EC2 API:
  New
Status in OpenStack Compute (Nova):
  Confirmed

Bug description:
  While creating volume, the return value says that volume creation time
  is dd-mm-yyThh:mm:ss.s, but while listing volumes at a later point
  of time, it changes to dd-mm-yyThh:mm:ss.0

  Doesn't look like a big issue though, but nevertheless shouldn't
  happen. I'd say the simplest solution should be to return dd-mm-
  yyThh:mm:ss.0 at the create-time itself.

To manage notifications about this bug go to:
https://bugs.launchpad.net/ec2-api/+bug/1280948/+subscriptions

-- 
Mailing list: https://launchpad.net/~yahoo-eng-team
Post to : yahoo-eng-team@lists.launchpad.net
Unsubscribe : https://launchpad.net/~yahoo-eng-team
More help   : https://help.launchpad.net/ListHelp