Back to bug 1574431

Who When What Removed Added
Thiago da Silva 2018-05-23 13:28:15 UTC Keywords Triaged
Priority unspecified low
Target Release --- 15.0 (S)
CC thiago
Severity medium low
Red Hat Bugzilla Rules Engine 2018-05-23 13:28:20 UTC Target Release 15.0 (S) ---
PnT Account Manager 2018-08-07 21:31:51 UTC CC thiago
Sean Cohen 2018-10-03 13:37:01 UTC CC scohen
Sean Cohen 2018-10-17 13:43:12 UTC Keywords Triaged
Target Milestone --- Upstream M2
Eric Harney 2018-10-25 15:25:40 UTC Keywords Triaged
CC eharney
Doc Text Cause: Usability issue in cinder client

Consequence: Users can apply quota commands that don't work as expected

Workaround (if any): Type the project ID instead of project name / other text

Result: Quota works as expected
Doc Type If docs needed, set a value Known Issue
Eric Harney 2018-11-15 08:04:19 UTC CC cchen
Alan Bishop 2018-11-28 13:49:42 UTC CC tshefi
Chuck Copello 2019-01-08 18:48:38 UTC Docs Contact knylande rhos-docs
Alex Stupnikov 2019-09-06 15:02:39 UTC CC astupnik
Giulio Fidente 2020-01-22 12:26:17 UTC CC gfidente
Target Milestone Upstream M2 z2
Greg Rakauskas 2020-01-30 20:44:03 UTC CC gregraka
Doc Text Cause: Usability issue in cinder client

Consequence: Users can apply quota commands that don't work as expected

Workaround (if any): Type the project ID instead of project name / other text

Result: Quota works as expected
There is a known issue for the Block Storage service (cinder) where quota commands do not work as expected. The cinder CLI allows users to successfully create quota entries without checking for a valid project ID. Quota entries that the CLI creates without valid project IDs are dummy records that contain invalid data. Until this issue is fixed, CLI users should make sure to specify a valid project ID when creating quota entries, and monitor cinder for dummy records.
Flags needinfo?(eharney)
Eric Harney 2020-03-19 15:16:58 UTC Link ID Launchpad 1307491
Tzach Shefi 2020-03-19 15:19:14 UTC QA Contact aavraham tshefi
Sofia Enriquez 2020-03-26 15:20:04 UTC CC senrique
Luigi Toscano 2020-04-06 16:31:44 UTC Target Milestone z2 ---
Greg Rakauskas 2020-04-06 18:42:50 UTC Flags needinfo?(eharney)
Luigi Toscano 2020-06-24 17:43:14 UTC Target Milestone --- z2
Alex McLeod 2020-07-03 17:15:05 UTC CC amcleod
Doc Text There is a known issue for the Block Storage service (cinder) where quota commands do not work as expected. The cinder CLI allows users to successfully create quota entries without checking for a valid project ID. Quota entries that the CLI creates without valid project IDs are dummy records that contain invalid data. Until this issue is fixed, CLI users should make sure to specify a valid project ID when creating quota entries, and monitor cinder for dummy records. There is a known issue for the Block Storage service (cinder) where quota commands do not work as expected. The cinder CLI allows users to successfully create quota entries without checking for a valid project ID. Quota entries that the CLI creates without valid project IDs are dummy records that contain invalid data. Until this issue is fixed, CLI users must specify a valid project ID when creating quota entries, and monitor cinder for dummy records.
Alex McLeod 2020-07-06 14:03:23 UTC Doc Text There is a known issue for the Block Storage service (cinder) where quota commands do not work as expected. The cinder CLI allows users to successfully create quota entries without checking for a valid project ID. Quota entries that the CLI creates without valid project IDs are dummy records that contain invalid data. Until this issue is fixed, CLI users must specify a valid project ID when creating quota entries, and monitor cinder for dummy records. Currently, quota commands do not work as expected in the Block Storage service (cinder). With the Block Storage CLI, you can successfully create quota entries and the CLI does not check for a valid project ID. Quota entries that the CLI creates without valid project IDs are dummy records that contain invalid data. Until this issue is fixed, if you are a CLI user, you must specify a valid project ID when you create quota entries and monitor Block Storage for dummy records.
Luigi Toscano 2020-08-24 14:29:40 UTC Target Milestone z2 z3
Greg Rakauskas 2020-08-24 14:30:58 UTC CC gregraka
Luigi Toscano 2020-10-21 13:29:14 UTC Target Milestone z3 z4
Luigi Toscano 2020-12-02 17:15:02 UTC Target Milestone z4 z5
Luigi Toscano 2021-03-24 12:44:08 UTC Target Milestone z5 z6
Luigi Toscano 2021-03-31 12:34:50 UTC Target Milestone z6 z7
Yaniv Kaul 2021-06-08 15:13:35 UTC CC ltoscano
Flags needinfo?(ltoscano)
Luigi Toscano 2021-06-08 15:28:03 UTC Flags needinfo?(ltoscano)
Eric Harney 2021-06-08 15:30:10 UTC Status NEW ON_DEV
Link ID OpenStack gerrit 784763
RHEL Program Management 2021-06-08 15:30:19 UTC Target Release --- 16.1 (Train on RHEL 8.2)
Luigi Toscano 2021-06-08 15:50:14 UTC Assignee cinder-bugs rdhasman
Luigi Toscano 2021-07-13 13:54:44 UTC Target Milestone z7 z8
Vincent S. Cojot 2021-07-15 19:14:42 UTC CC vcojot
Red Hat One Jira (issues.redhat.com) 2021-12-10 16:21:02 UTC Link ID Red Hat Issue Tracker OSP-718
Luigi Toscano 2022-01-10 18:19:12 UTC Target Milestone z8 z9
Red Hat Bugzilla 2022-11-24 08:37:23 UTC Docs Contact rhos-docs astillma
Jenny-Anne Lynch 2022-12-05 13:07:46 UTC Doc Text Currently, quota commands do not work as expected in the Block Storage service (cinder). With the Block Storage CLI, you can successfully create quota entries and the CLI does not check for a valid project ID. Quota entries that the CLI creates without valid project IDs are dummy records that contain invalid data. Until this issue is fixed, if you are a CLI user, you must specify a valid project ID when you create quota entries and monitor Block Storage for dummy records. Currently, quota commands do not work as expected in the Block Storage service (cinder). The Block Storage CLI does not verify if the project ID that you specify is valid. Therefore, you can use the Block Storage CLI to create quota entries with invalid project IDs. These quota entries are dummy records that contain invalid data. Until this issue is fixed, if you are a CLI user, you must specify a valid project ID when you create quota entries and monitor Block Storage for dummy records.
CC jelynch
Luigi Toscano 2022-12-08 22:27:53 UTC QA Contact tshefi eshames
Jenny-Anne Lynch 2023-01-18 10:38:56 UTC CC jelynch
Eric Harney 2023-02-13 19:29:58 UTC Target Milestone z9 ---
Target Release 16.1 (Train on RHEL 8.2) 18.0
RHEL Program Management 2023-02-13 19:30:08 UTC Target Release 18.0 ---
Red Hat Bugzilla 2023-07-29 08:27:36 UTC CC senrique
Tzach Shefi 2023-07-30 06:52:41 UTC CC tshefi

Back to bug 1574431