← Back to team overview

yahoo-eng-team team mailing list archive

[Bug 1503027] [NEW] default security group creation ignores quota_usages conf

 

Public bug reported:

There is a configuration setting that affects the creation of
quota_usages entries for resource tracking, until_refresh.  This setting
is a count of the number of quota updates to allow before doing a sync
of quota_usages to ensure that it is correct.  The configuration value
operates by being written into the quota_usages table when a row is
created, and then it is used/modified by quota tracking code thereafter.
If the value of until_refresh in the db row is None then the quota will
never be checked against the actual usage and is at risk of drifting
from the true usage value.

When an instance boot request occurs part of the process is to ensure
that there is a default security group created for a project.  If there
is no default then one is created and a quota_usages entry is created to
track the usage of the security group by the project.  This quota_usages
creation sets until_refresh to None and completely ignore the
configuration value that should affect that value.

** Affects: nova
     Importance: Undecided
     Assignee: Andrew Laski (alaski)
         Status: In Progress

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

Title:
  default security group creation ignores quota_usages conf

Status in OpenStack Compute (nova):
  In Progress

Bug description:
  There is a configuration setting that affects the creation of
  quota_usages entries for resource tracking, until_refresh.  This
  setting is a count of the number of quota updates to allow before
  doing a sync of quota_usages to ensure that it is correct.  The
  configuration value operates by being written into the quota_usages
  table when a row is created, and then it is used/modified by quota
  tracking code thereafter.  If the value of until_refresh in the db row
  is None then the quota will never be checked against the actual usage
  and is at risk of drifting from the true usage value.

  When an instance boot request occurs part of the process is to ensure
  that there is a default security group created for a project.  If
  there is no default then one is created and a quota_usages entry is
  created to track the usage of the security group by the project.  This
  quota_usages creation sets until_refresh to None and completely ignore
  the configuration value that should affect that value.

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


Follow ups