| Thread Previous • Date Previous • Date Next • Thread Next |
Public bug reported:
The message is "InvalidBDM: Block Device Mapping is Invalid." Exceeding
quota is a problem that should be solved by the user, not a cloud admin.
So the message should be one telling the user that the error was caused
by quota.
Example:
A user has 2 GB of volume quota.
ubuntu@dev-1:~/devstack$ cinder quota-usage b926f718a7d345cb9f57b4e4dc98f674
+-----------------------+--------+----------+-------+
| Type | In_use | Reserved | Limit |
+-----------------------+--------+----------+-------+
| backup_gigabytes | 0 | 0 | 1000 |
| backups | 0 | 0 | 10 |
| gigabytes | 0 | 0 | 2 |
| gigabytes_lvmdriver-1 | 0 | 0 | 2 |
| per_volume_gigabytes | 0 | 0 | -1 |
| snapshots | 0 | 0 | 10 |
| snapshots_lvmdriver-1 | 0 | 0 | -1 |
| volumes | 0 | 0 | 10 |
| volumes_lvmdriver-1 | 0 | 0 | -1 |
+-----------------------+--------+----------+-------+
Then, create an instance with 3 GB volume creation
ubuntu@dev-1:~/devstack$ nova boot --flavor m1.tiny --block-device source=image,id=535ec234-5522-4cdc-598-4050a62d5135,dest=volume,size=3,bootindex=0 vb
+--------------------------------------+-------------------------------------------------+
| Property | Value |
+--------------------------------------+-------------------------------------------------+
| OS-DCF:diskConfig | MANUAL |
| OS-EXT-AZ:availability_zone | nova |
| OS-EXT-STS:power_state | 0 |
| OS-EXT-STS:task_state | scheduling |
| OS-EXT-STS:vm_state | building |
| OS-SRV-USG:launched_at | - |
| OS-SRV-USG:terminated_at | - |
| accessIPv4 | |
| accessIPv6 | |
| adminPass | znMzRMuCJx99 |
| config_drive | |
| created | 2015-08-06T11:34:53Z |
| flavor | m1.tiny (1) |
| hostId | |
| id | 5934a4f5-4d89-465b-956b-f53b2ebdad43 |
| image | Attempt to boot from volume - no image supplied |
| key_name | - |
| metadata | {} |
| name | vb |
| os-extended-volumes:volumes_attached | [] |
| progress | 0 |
| security_groups | default |
| status | BUILD |
| tenant_id | b926f718a7d345cb9f57b4e4dc98f674 |
| updated | 2015-08-06T11:34:54Z |
| user_id | 386255bb3f05410dae7856633f0e611e |
+--------------------------------------+-------------------------------------------------+
Fails with a message "Failure prepping block device". It is difficult to
know the quota is a cause of the error by seeing the message.
ubuntu@dev-1:~/devstack$ nova show vb
+--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Property | Value |
+--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------+
| OS-DCF:diskConfig | MANUAL |
| OS-EXT-AZ:availability_zone | nova |
| OS-EXT-STS:power_state | 0 |
| OS-EXT-STS:task_state | block_device_mapping |
| OS-EXT-STS:vm_state | error |
| OS-SRV-USG:launched_at | - |
| OS-SRV-USG:terminated_at | - |
| accessIPv4 | |
| accessIPv6 | |
| config_drive | |
| created | 2015-08-06T11:34:53Z |
| fault | {"message": "Build of instance 5934a4f5-4d89-465b-956b-f53b2ebdad43 aborted: Failure prepping block device.", "code": 500, "created": "2015-08-06T11:34:58Z"} |
| flavor | m1.tiny (1) |
| hostId | c44fcd09b907ebe036f7d5e486e6392f06a46af3a333abd0160c972d |
| id | 5934a4f5-4d89-465b-956b-f53b2ebdad43 |
| image | Attempt to boot from volume - no image supplied |
| key_name | - |
| metadata | {} |
| name | vb |
| os-extended-volumes:volumes_attached | [] |
| private network | 10.0.0.2 |
| security_groups | default |
| status | ERROR |
| tenant_id | b926f718a7d345cb9f57b4e4dc98f674 |
| updated | 2015-08-06T11:34:58Z |
| user_id | 386255bb3f05410dae7856633f0e611e |
+--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------+
** Affects: nova
Importance: Undecided
Assignee: Arata Notsu (arata776)
Status: In Progress
--
You received this bug notification because you are a member of Yahoo!
Engineering Team, which is subscribed to OpenStack Compute (nova).
https://bugs.launchpad.net/bugs/1482191
Title:
Error message is too generic when boot with volume creation fails with
exceeded quota
Status in OpenStack Compute (nova):
In Progress
Bug description:
The message is "InvalidBDM: Block Device Mapping is Invalid."
Exceeding quota is a problem that should be solved by the user, not a
cloud admin. So the message should be one telling the user that the
error was caused by quota.
Example:
A user has 2 GB of volume quota.
ubuntu@dev-1:~/devstack$ cinder quota-usage b926f718a7d345cb9f57b4e4dc98f674
+-----------------------+--------+----------+-------+
| Type | In_use | Reserved | Limit |
+-----------------------+--------+----------+-------+
| backup_gigabytes | 0 | 0 | 1000 |
| backups | 0 | 0 | 10 |
| gigabytes | 0 | 0 | 2 |
| gigabytes_lvmdriver-1 | 0 | 0 | 2 |
| per_volume_gigabytes | 0 | 0 | -1 |
| snapshots | 0 | 0 | 10 |
| snapshots_lvmdriver-1 | 0 | 0 | -1 |
| volumes | 0 | 0 | 10 |
| volumes_lvmdriver-1 | 0 | 0 | -1 |
+-----------------------+--------+----------+-------+
Then, create an instance with 3 GB volume creation
ubuntu@dev-1:~/devstack$ nova boot --flavor m1.tiny --block-device source=image,id=535ec234-5522-4cdc-598-4050a62d5135,dest=volume,size=3,bootindex=0 vb
+--------------------------------------+-------------------------------------------------+
| Property | Value |
+--------------------------------------+-------------------------------------------------+
| OS-DCF:diskConfig | MANUAL |
| OS-EXT-AZ:availability_zone | nova |
| OS-EXT-STS:power_state | 0 |
| OS-EXT-STS:task_state | scheduling |
| OS-EXT-STS:vm_state | building |
| OS-SRV-USG:launched_at | - |
| OS-SRV-USG:terminated_at | - |
| accessIPv4 | |
| accessIPv6 | |
| adminPass | znMzRMuCJx99 |
| config_drive | |
| created | 2015-08-06T11:34:53Z |
| flavor | m1.tiny (1) |
| hostId | |
| id | 5934a4f5-4d89-465b-956b-f53b2ebdad43 |
| image | Attempt to boot from volume - no image supplied |
| key_name | - |
| metadata | {} |
| name | vb |
| os-extended-volumes:volumes_attached | [] |
| progress | 0 |
| security_groups | default |
| status | BUILD |
| tenant_id | b926f718a7d345cb9f57b4e4dc98f674 |
| updated | 2015-08-06T11:34:54Z |
| user_id | 386255bb3f05410dae7856633f0e611e |
+--------------------------------------+-------------------------------------------------+
Fails with a message "Failure prepping block device". It is difficult
to know the quota is a cause of the error by seeing the message.
ubuntu@dev-1:~/devstack$ nova show vb
+--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------+
| Property | Value |
+--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------+
| OS-DCF:diskConfig | MANUAL |
| OS-EXT-AZ:availability_zone | nova |
| OS-EXT-STS:power_state | 0 |
| OS-EXT-STS:task_state | block_device_mapping |
| OS-EXT-STS:vm_state | error |
| OS-SRV-USG:launched_at | - |
| OS-SRV-USG:terminated_at | - |
| accessIPv4 | |
| accessIPv6 | |
| config_drive | |
| created | 2015-08-06T11:34:53Z |
| fault | {"message": "Build of instance 5934a4f5-4d89-465b-956b-f53b2ebdad43 aborted: Failure prepping block device.", "code": 500, "created": "2015-08-06T11:34:58Z"} |
| flavor | m1.tiny (1) |
| hostId | c44fcd09b907ebe036f7d5e486e6392f06a46af3a333abd0160c972d |
| id | 5934a4f5-4d89-465b-956b-f53b2ebdad43 |
| image | Attempt to boot from volume - no image supplied |
| key_name | - |
| metadata | {} |
| name | vb |
| os-extended-volumes:volumes_attached | [] |
| private network | 10.0.0.2 |
| security_groups | default |
| status | ERROR |
| tenant_id | b926f718a7d345cb9f57b4e4dc98f674 |
| updated | 2015-08-06T11:34:58Z |
| user_id | 386255bb3f05410dae7856633f0e611e |
+--------------------------------------+---------------------------------------------------------------------------------------------------------------------------------------------------------------+
To manage notifications about this bug go to:
https://bugs.launchpad.net/nova/+bug/1482191/+subscriptions
| Thread Previous • Date Previous • Date Next • Thread Next |
