Hi Volodymyr,
I didn't really try to reproduce this, but here's an excerpt from a
template we have been using successfully:
---cut here---
[...]
vm-vda:
type: OS::Cinder::Volume
properties:
description: VM vda
image: image-vda
name: disk-vda
size: 100
vm-vd
Hi again,
there is similar case - https://bugs.launchpad.net/nova/+bug/1570107 -
but I get same result (booting from VOLUME2) regardless of whether I use
or don't use device_type/disk_bus properties in BDM description.
Any ideas on how to solve this issue?
Thanks.
On 9/11/18 10:58 AM, Volod
Hi colleagues,
is there any mechanism to ensure boot disk when attaching more than two
volumes to server? At the moment, I can't find a way to make it predictable.
I have two bootable images with the following properties:
1) hw_boot_menu='true', hw_disk_bus='scsi', hw_qemu_guest_agent='yes',
