yahoo-eng-team team mailing list archive

[Launchpad Bug Tracker <1160749@xxxxxxxxxxxxxxxxxx>]

You have been subscribed to a public bug:

1. Changed number of the cores from 100 to 15 with the following
command:

[root@firstbox11-1 ˜]# nova quota-update --cores 15 2bff6058d6454dc0859cc545c2dc6d4f
[root@firstbox11-1 ˜]# nova quota-show 2bff6058d6454dc0859cc545c2dc6d4f
+-----------------------------+--------+
| Property                    | Value  |
+-----------------------------+--------+
| cores                       | 15     |
| floating_ips                | 40     |
| gigabytes                   | 1000   |
| injected_file_content_bytes | 10240  |
| injected_files              | 5      |
| instances                   | 100    |
| metadata_items              | 128    |
| ram                         | 204800 |
| volumes                     | 10     |
+-----------------------------+--------+

2. Perform a deploy using a flavor with 8 CPUs like this:

tm_fl: Memory: 2048MB, VCPUS: 8, Root: 8GB, Ephemeral: 0Gb, FlavorID:
69, Swap: 0MB, RXTX Factor: 1.0, public, ExtraSpecs {}

the deploy fails with the following message:
'Quota exceeded for cores: Requested 8, but already used 47 of 15 cores'

This is an issue, because 47 cores are already used, but the nova quota-update does not check and permits to decrease the cores value under
47.....in alternative if it is possible have a number of cores already used greater than of the cores defined on quota....it is an usability issue because minimum a warning should be issued when nova quota-update is issued.

** Affects: nova
     Importance: Undecided
     Assignee: David Geng (genggjh)
         Status: In Progress

-- 
nova quota-update command is executed without checking if the quota exceed
https://bugs.launchpad.net/bugs/1160749
You received this bug notification because you are a member of Yahoo! Engineering Team, which is subscribed to OpenStack Compute (nova).