cinder quota update didn't validate its parameter <tenant_ID>

Bug #1686973 reported by Saurabh jangir on 2017-04-28
14
This bug affects 3 people
Affects Status Importance Assigned to Milestone
Cinder
Undecided
Unassigned

Bug Description

Cinder quota update command is accepting invalid tenant-ID and updating quota as well.

Please find the terminal output.

[root@localhost ~(keystone_admin)]# cinder quota-update --per-volume-gigabytes 1 1
+----------------------+-------+
| Property | Value |
+----------------------+-------+
| backup_gigabytes | 1000 |
| backups | 10 |
| gigabytes | 1000 |
| gigabytes_iscsi | -1 |
| per_volume_gigabytes | 1 |
| snapshots | 10 |
| snapshots_iscsi | -1 |
| volumes | 10 |
| volumes_iscsi | -1 |
+----------------------+-------+

[root@localhost ~(keystone_admin)]# cinder quota-update --per-volume-gigabytes 2 5dcff0e2e2c34730ab1322e
+----------------------+-------+
| Property | Value |
+----------------------+-------+
| backup_gigabytes | 1000 |
| backups | 10 |
| gigabytes | 1000 |
| gigabytes_iscsi | -1 |
| per_volume_gigabytes | 2 |
| snapshots | 10 |
| snapshots_iscsi | -1 |
| volumes | 10 |
| volumes_iscsi | -1 |

I am using cinder version:

[root@localhost ~(keystone_admin)]# cinder --version
1.11.0

tags: added: cinder
Changed in cinder:
status: New → Confirmed
To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers