until_refresh act strange

Bug #1697906 reported by xhzhf on 2017-06-14
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Cinder
Undecided
Gorka Eguileor

Bug Description

If until_refresh of a tenant is None and we modify configuration file to set until_refresh equal 1, then the until_refresh property will not change after adding a new volume.
It means that modifying until_reshresh from None to 1 does not work to existing tenant.

If until_refresh of a tenant is 1 and we modify configuration file to set until_refresh equal None, then the until_refresh property will change to None after adding a new volume.
It means that modifying until_reshresh from 1 to None does work to existing tenant.

I think the situation will make openstackers confused.

The inner reason is that if only when refresh of a tenant is 1, refresh will be triggered.

the related function is quota_reserver in /cinder/db/sqlalchemy/api.py

xhzhf (guoyongxhzhf) on 2017-06-14
Changed in cinder:
assignee: nobody → xhzhf (guoyongxhzhf)
Revision history for this message
Sean McGinnis (sean-mcginnis) wrote : Bug Assignee Expired

Unassigning due to no activity for > 6 months.

Changed in cinder:
assignee: xhzhf (guoyongxhzhf) → nobody
Gorka Eguileor (gorka) on 2021-03-02
tags: added: quotas
Revision history for this message
Gorka Eguileor (gorka) wrote :
Gorka Eguileor (gorka) on 2021-03-10
Changed in cinder:
assignee: nobody → Gorka Eguileor (gorka)
status: New → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/cinder 18.0.0.0rc2

This issue was fixed in the openstack/cinder 18.0.0.0rc2 release candidate.

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

Other bug subscribers