yahoo-eng-team team mailing list archive

["Markus Zoeller \(markus_z\)" <mzoeller@xxxxxxxxxxxxxxxxxx>]

This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.

If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
  Only still supported release names are valid (LIBERTY, MITAKA, OCATA, NEWTON).
  Valid example: CONFIRMED FOR: LIBERTY


** Changed in: nova
   Importance: Low => Undecided

** Changed in: nova
       Status: Confirmed => Expired

-- 
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/1254980

Title:
  Fix null value for updated time

Status in OpenStack Compute (nova):
  Expired

Bug description:
  Updated time is null value in response body while updating
  "availability_zone" for aggregate only.

  There are two tables "aggregates" and "aggregate_metadata",if you call
  the update_aggregate api to update the "availability_zone" for
  aggregate, the  tables "aggregates" hasn't been updated, so the
  updated_time is null value in response body  which get from tables
  "aggregates" .But for user, the aggregate is updated, why the
  updated_time is null?

  Also, get and list has the same problem.

  I think it's a bug.

To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1254980/+subscriptions