instance‘s root_gb is 0, but the actual root_gb size is not 0.
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Won't Fix
|
Wishlist
|
Unassigned |
Bug Description
1. I have a flavor named 'disk0' that's disk size is 0.
[root@opencos11
+------
| ID | Name | Memory_MB | Disk | Ephemeral | Swap | VCPUs | RXTX_Factor | Is_Public |
+------
| 1 | m1.tiny | 512 | 1 | 0 | | 1 | 1.0 | True |
| 2 | m1.small | 2048 | 20 | 0 | | 1 | 1.0 | True |
| 3 | m1.medium | 4096 | 40 | 0 | | 2 | 1.0 | True |
| 4 | m1.large | 8192 | 80 | 0 | | 4 | 1.0 | True |
| 41ef4850-
| 5 | m1.xlarge | 16384 | 160 | 0 | | 8 | 1.0 | True |
+------
2. I use disk0 flavor to boot a instance and instance' uuid is 9fb1389d-
[root@opencos11
+------
| Property | Value |
+------
| OS-DCF:diskConfig | MANUAL |
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-
| OS-EXT-STS:vm_state | building |
| OS-SRV-
| OS-SRV-
| accessIPv4 | |
| accessIPv6 | |
| adminPass | Q5iUAxTW5r29 |
| config_drive | |
| created | 2015-03-
| flavor | disk0 (41ef4850-
| hostId | |
| id | 9fb1389d-
| image | cirror (66d2336c-
| key_name | - |
| metadata | {} |
| name | hanrong |
| os-extended-
| progress | 0 |
| security_groups | default |
| serial_type | file |
| status | BUILD |
| tenant_id | 94d1a1b3260648f
| updated | 2015-03-
| user_id | 1f60084b664844a
+------
3. I see the instance's root_gb is 0 in nova database.
[root@opencos11
Welcome to the MariaDB monitor. Commands end with ; or \g.
Your MariaDB connection id is 9905
Server version: 5.5.36-
Copyright (c) 2000, 2013, Oracle, Monty Program Ab and others.
Type 'help;' or '\h' for help. Type '\c' to clear the current input statement.
MariaDB [(none)]> use nova
Reading table information for completion of table and column names
You can turn off this feature to get a quicker startup with -A
Database changed
MariaDB [nova]> select uuid,root_gb from instances where uuid='9fb1389d-
+------
| uuid | root_gb |
+------
| 9fb1389d-
+------
1 row in set (0.00 sec)
4. But this instance's actual root disk size is not 0.
[root@opencos114-98 instances]# cd 9fb1389d-
[root@opencos114-98 9fb1389d-
total 992
-rw-rw---- 1 root root 16750 Mar 28 16:39 console.log
-rw-r--r-- 1 root root 1048576 Mar 28 16:39 disk
-rw-r--r-- 1 root root 79 Mar 28 16:38 disk.info
-rw-r--r-- 1 root root 1725 Mar 28 16:38 libvirt.xml
[root@opencos114-98 9fb1389d-
image: disk
file format: qcow2
virtual size: 39M (41126400 bytes)
disk size: 1.3M
cluster_size: 65536
backing file: /var/lib/
Format specific information:
compat: 1.1
lazy refcounts: false
5. Many disk statistics are resulting from instances' root_gb field. I think 0 is improper, image's virtual size would be more appropriate.
description: | updated |
Changed in nova: | |
assignee: | nobody → Meena (meena-ventrapati) |
Changed in nova: | |
assignee: | Meena (meena-ventrapati) → nobody |
tags: | added: scheduler |
tags: | added: compute |
description: | updated |
Changed in nova: | |
assignee: | nobody → Charlotte Han (hanrong) |
Changed in nova: | |
status: | Won't Fix → In Progress |
Changed in nova: | |
assignee: | Charlotte Han (hanrong) → nobody |
status: | In Progress → Won't Fix |
Hi,
I do not think that this is a bug. When the flavor size is 0 then the driver will make use of the size of the image that is downloaded.
Thanks
Gary