This is because the time it takes to create the volume is longer than
the default timeout value. You can increase the timeout value in
/etc/nova/nova.conf to something greater, e.g. 3600.
block_device_allocate_retries = 3600
** Changed in: nova
Status: Confirmed = Invalid
--
You
** Also affects: cinder
Importance: Undecided
Status: New
** Changed in: cinder
Assignee: (unassigned) = Thang Pham (thang-pham)
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net
** Changed in: nova
Importance: Undecided = Medium
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1313935
Title:
tenant is required for quota-update but not for quota-show
To
** Changed in: nova
Status: New = In Progress
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1313935
Title:
tenant is required for quota-update but not for quota-show
To
The problem is nova quota-update uses value of tenant-id to save the
quota in the database. If you use demo as the tenant-id, nova will
use project_id=demo when setting the project_user_quotas table. If
you use a uuid as the tenant-id, nova will use project_id=uuid when
setting the
Another solution is: check that the tenant-id is actually a valid
uuid.
--
You received this bug notification because you are a member of Ubuntu
Server Team, which is subscribed to nova in Ubuntu.
https://bugs.launchpad.net/bugs/1313935
Title:
tenant is required for quota-update but not for
