yahoo-eng-team team mailing list archive

[Chris Dent <cdent+lp@xxxxxxxxxxxxx>]

Public bug reported:

When listing allocations by resource provider or consumer uuid, the
updated_at and created_at fields in the database are not loaded into the
object, so default to now when their times are used to generate last-
modified headers in http responses.

This isn't a huge problem because we tend not to care about those times
(at the moment), but it would be a useful thing to clean up.

The issues are in AllocationList.get_all_by_resource_provider and
.get_all_by_consumer_id

** Affects: nova
     Importance: Low
         Status: New


** Tags: placement

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

Title:
  allocations by consumer and resource provider use wrong timestamp

Status in OpenStack Compute (nova):
  New

Bug description:
  When listing allocations by resource provider or consumer uuid, the
  updated_at and created_at fields in the database are not loaded into
  the object, so default to now when their times are used to generate
  last-modified headers in http responses.

  This isn't a huge problem because we tend not to care about those
  times (at the moment), but it would be a useful thing to clean up.

  The issues are in AllocationList.get_all_by_resource_provider and
  .get_all_by_consumer_id

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