← Back to team overview

jiocloud-devops team mailing list archive

[Bug 1460605] [NEW] [nova-quota] Frequent updation of Tempest quota

 

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

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

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


jas@st7:~$ nova quota-show
+-----------------------------+--------+
| Quota                       | Limit  |
+-----------------------------+--------+
| instances                   | 20     |
| cores                       | 150    |
| ram                         | 150000 |
| 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     |
+-----------------------------+--------+
jas@st7:~$ nova quota-show
+-----------------------------+--------+
| Quota                       | Limit  |
+-----------------------------+--------+
| instances                   | 50     |
| cores                       | 150    |
| ram                         | 150000 |
| 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     |
+-----------------------------+--------+
jas@st7:~$ date
Mon Jun  1 15:56:34 IST 2015
jas@st7:~$ nova quota-show

** Affects: jio
     Importance: Critical
     Assignee: Reliance Jio DevOps (jiocloud-devops)
         Status: New


** Tags: operational-issue
-- 
[nova-quota] Frequent updation of Tempest quota 
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.