Bug 1574431
Summary: | cinder quota-update command accepts incorrect project IDs | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Alex Stupnikov <astupnik> |
Component: | openstack-cinder | Assignee: | Rajat Dhasmana <rdhasman> |
Status: | CLOSED MIGRATED | QA Contact: | Yosi Ben Shimon <ybenshim> |
Severity: | low | Docs Contact: | RHOS Documentation Team <rhos-docs> |
Priority: | low | ||
Version: | 10.0 (Newton) | CC: | amcleod, astupnik, cchen, eharney, gfidente, ltoscano, scohen, srevivo, udesale, vcojot, yrabl |
Target Milestone: | --- | Keywords: | Triaged |
Target Release: | --- | ||
Hardware: | x86_64 | ||
OS: | Linux | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Known Issue | |
Doc Text: |
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.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2024-01-05 12:24:55 UTC | Type: | Bug |
Regression: | --- | Mount Type: | --- |
Documentation: | --- | CRM: | |
Verified Versions: | Category: | --- | |
oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
Cloudforms Team: | --- | Target Upstream Version: | |
Embargoed: |
Description
Alex Stupnikov
2018-05-03 10:20:46 UTC
*** Bug 1650027 has been marked as a duplicate of this bug. *** *** Bug 1653755 has been marked as a duplicate of this bug. *** It's interesting this is low/low, considering we have 2 customer cases here, and it's a usability issue. Do we have any forecast for fixing this? (In reply to Yaniv Kaul from comment #8) > It's interesting this is low/low, considering we have 2 customer cases here, > and it's a usability issue. Do we have any forecast for fixing this? Not at the moment, but it still useful to be fixed. Also seeing that on OSP13: overcloud) [stack@director ~]$ cinder quota-update --volumes -1 ma_soeur +----------------------+-------+ | Property | Value | +----------------------+-------+ | backup_gigabytes | 1000 | | backups | 10 | | gigabytes | 1000 | | gigabytes_ontap | -1 | | gigabytes_solidfire | -1 | | groups | 10 | | per_volume_gigabytes | -1 | | snapshots | 10 | | snapshots_ontap | -1 | | snapshots_solidfire | -1 | | volumes | -1 | | volumes_ontap | -1 | | volumes_solidfire | -1 | +----------------------+-------+ (overcloud) [stack@director ~]$ 3:11 (overcloud) [stack@director ~]$ cinder quota-show ma_soeur +----------------------+-------+ | Property | Value | +----------------------+-------+ | backup_gigabytes | 1000 | | backups | 10 | | gigabytes | 1000 | | gigabytes_ontap | -1 | | gigabytes_solidfire | -1 | | groups | 10 | | per_volume_gigabytes | -1 | | snapshots | 10 | | snapshots_ontap | -1 | | snapshots_solidfire | -1 | | volumes | -1 | | volumes_ontap | -1 | | volumes_solidfire | -1 | +----------------------+-------+ (overcloud) [stack@director ~]$ openstack project show ma_soeur No project with a name or ID of 'ma_soeur' exists. |