Nova quotas update for large values erroneous

[Abhishek Sharma M]

When we update nova related quota values with larger values, the updated value is not what we expected.

For example,
1. If we try to update virtual machines quota to 2147483647, the vm quota gets updated to 2147480000.
2. If we try to update virtual machines quota to 2147479 or 2147481, the vm quota gets updated to 2147480.
3. Similar to above examples there are several values in that range where the update behaves not as expected.

[Dinesh Bhor (dinesh-bhor)]

Hi Abhishek,

I am not able to reproduce this issue on my environment.
For me the quota-update is working fine.

Could you please give some more information of the nova version, and some logs may be?

[Abhishek Sharma M (abhi.sharma)]

Hi Dinesh

I am using nova 15.0.4
quota-update works fine unless for the values which I have mentioned in the problem statement. Did you try to update any nova related quota with 2147483647 or 2147481 values & observed the updated value?
Logs do not show any warning or errors as the update is happening successfully.

[Ritesh Paiboina (rsritesh)]

Hi,

What are you steps :

For me , its being updated correctly

$ nova quota-update 45cbd753bde2440bb4072b15074da425 --instances 2147483647

$ nova quota-show --tenant 45cbd753bde2440bb4072b15074da425
+-----------------------------+------------+
| Quota | Limit |
+-----------------------------+------------+
| instances | 2147483647 |
| cores | 20 |
| ram | 51200 |
| metadata_items | 128 |
| injected_files | 5 |
| injected_file_content_bytes | 10240 |
| injected_file_path_bytes | 255 |
| key_pairs | 100 |
| server_groups | 10 |
| server_group_members | 10 |
+-----------------------------+------------+

$ nova --version
7.1.0

[Abhishek Sharma M (abhi.sharma)]

The issue is with the database schema we were using. We used float to store the values, this is where it was getting messed up. Using 'int' or 'double' solves this.

Please ignore this defect.