failed to attach volumes to instances after configuration change & services restart
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
OpenStack Compute (nova) |
Invalid
|
Undecided
|
Unassigned |
Bug Description
Description of problem:
The attachment of volumes failed with the errors that are available in the log file attached. Prior to the error I was running 8 active instances, made a configuration change - increased the number of workers in the Cinder, Nova & Glance services, then restarted the services.
Ran the command:
# nova volume-attach 6aac6fb6-
+------
| Property | Value |
+------
| device | /dev/vdc |
| id | 57edbc5c-
| serverId | 6aac6fb6-
| volumeId | 57edbc5c-
+------
cinder list output:
+-----
| ID | Status | Display Name | Size | Volume Type | Bootable | Attached to |
+------
| 57edbc5c-
| 731a118d-
+------
Version-Release number of selected component (if applicable):
python-
openstack-
python-
openstack-
openstack-
python-
openstack-
openstack-
openstack-
openstack-
openstack-
openstack-
python-
openstack-
How reproducible:
100%
Steps to Reproduce:
1. Launch instances
2. Increase the number of workers for the Cinder, Nova & Glance
3. Create a volume
4. Attach the volume to the instance.
Actual results:
The attachment process fail.
Expected results:
The volume should be attached to the instance.
Changed in nova: | |
status: | Incomplete → Invalid |
As a workaround, with new instances the volume are been attached.