[vCenter] Volume is attached only after reboot instance
Bug #1526235 reported by
Ilya Bumarskov
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| Fuel for OpenStack |
Invalid
|
High
|
Alexander Arzhanov | ||
| 7.0.x |
Invalid
|
High
|
Alexander Arzhanov | ||
Bug Description
ISO #291
Volume from cinder-vmware availability zone can be attached only after reboot instance (vcenter availability zone).
Enviroment:
Compute: QEMU + vCenter
Networking Setup: Neutron with VLAN segmentation + DVS plugin
Storage backends: default
Additional services: all by default
Nodes:
Controller
Cinder-vmware
| Changed in fuel: | |
| importance: | Undecided → Medium |
| assignee: | nobody → Alexander Arzhanov (aarzhanov) |
| milestone: | none → 8.0 |
| importance: | Medium → High |
| tags: | added: area-partners vcenter |
| Changed in fuel: | |
| status: | New → Triaged |
Revision history for this message
| Alexander Arzhanov (aarzhanov) wrote | #1 |
| Changed in fuel: | |
| status: | Triaged → Invalid |
To post a comment you must log in.
http://
When a volume is attached to an instance, a reconfigure operation is performed on the instance to add the volume's VMDK to it. The user must manually rescan and mount the device from within the guest operating system.