← Back to team overview

jiocloud-devops team mailing list archive

[Bug 1460605] [NEW] [nova-quota] Inconsitent quota behavour

 

Mayank Kapoor (mayankkapoor) has assigned this bug to you for Jio:

Nova is switching instance quota for tenant between 20 and 50.

We observed this issue with tempest and tenants created via Dashboard
registration flow.

Steps to reproduce
1) source openrc
2) run nova quota-show  command few times.

manasi@st7:~$ nova quota-show
+-----------------------------+-------+
| Quota                       | Limit |
+-----------------------------+-------+
| instances                   | 50    |
| cores                       | 100   |
| ram                         | 51200 |
| floating_ips                | 10    |
| fixed_ips                   | -1    |
| metadata_items              | 128   |
| injected_files              | 5     |
| injected_file_content_bytes | 10240 |
| injected_file_path_bytes    | 255   |
| key_pairs                   | 10    |
| security_groups             | 10    |
| security_group_rules        | 20    |
+-----------------------------+-------+
manasi@st7:~$ nova quota-show
+-----------------------------+-------+
| Quota                       | Limit |
+-----------------------------+-------+
| instances                   | 20    |
| cores                       | -1    |
| ram                         | -1    |
| floating_ips                | 10    |
| fixed_ips                   | -1    |
| metadata_items              | 128   |
| injected_files              | 5     |
| injected_file_content_bytes | 10240 |
| injected_file_path_bytes    | 255   |
| key_pairs                   | 10    |
| security_groups             | 10    |
| security_group_rules        | 20    |
+-----------------------------+-------+
manasi@st7:~$

** Affects: jio
     Importance: High
     Assignee: Reliance Jio DevOps (jiocloud-devops)
         Status: Triaged


** Tags: operational-issue
-- 
[nova-quota] Inconsitent quota behavour
https://bugs.launchpad.net/bugs/1460605
You received this bug notification because you are a member of Reliance Jio DevOps, which is a bug assignee.