Cannot boot instance from volume snapshot

I'll be available on New Year holidays, so I assign it on nova team until January 11. I tried to reproduce it on the following environment but it didn't reproduce.

1 controller

2 compute

Ceph all

I tried this on ISO #364 and it works like a charm. Log of shell session: http://paste.openstack.org/show/482949/

Nova/Cinder packages used:

root@node-1:~# dpkg -l | grep nova
ii nova-api 2:12.0.0-1~u14.04+mos19 all OpenStack Compute - compute API frontend
ii nova-cert 2:12.0.0-1~u14.04+mos19 all OpenStack Compute - certificate manager
ii nova-common 2:12.0.0-1~u14.04+mos19 all OpenStack Compute - common files
ii nova-conductor 2:12.0.0-1~u14.04+mos19 all OpenStack Compute - conductor service
ii nova-consoleauth 2:12.0.0-1~u14.04+mos19 all OpenStack Compute - Console Authenticator
ii nova-consoleproxy 2:12.0.0-1~u14.04+mos19 all OpenStack Compute - NoVNC proxy
ii nova-objectstore 2:12.0.0-1~u14.04+mos19 all OpenStack Compute - object store
ii nova-scheduler 2:12.0.0-1~u14.04+mos19 all OpenStack Compute - virtual machine scheduler
ii python-nova 2:12.0.0-1~u14.04+mos19 all OpenStack Compute - libraries
ii python-novaclient 2:2.30.2-1~u14.04+mos3 all client library for OpenStack Compute API
root@node-1:~# dpkg -l | grep cinder
ii cinder-api 2:7.0.1-1~u14.04+mos7 all OpenStack block storage system - API server
ii cinder-backup 2:7.0.1-1~u14.04+mos7 all OpenStack block storage system - Backup server
ii cinder-common 2:7.0.1-1~u14.04+mos7 all OpenStack block storage system - common files
ii cinder-scheduler 2:7.0.1-1~u14.04+mos7 all OpenStack block storage system - Scheduler server
ii cinder-volume 2:7.0.1-1~u14.04+mos7 all OpenStack block storage system - Volume server
ii python-cinder 2:7.0.1-1~u14.04+mos7 all OpenStack block storage system - Python libraries
ii python-cinderclient 1:1.4.0-1~u14.04+mos2 all Python bindings to the OpenStack Volume API - Python 2.x

^ Ceph was used for volumes:

root@node-1:~# grep volume_driver /etc/cinder/cinder.conf
volume_driver=cinder.volume.drivers.rbd.RBDDriver

Sergey, I also checked logs you provided in #1: looks like they have been stripped somehow - request IDs and exception tracebacks are missing. Unfortunately, InvalidBDM is the most general exception in the class hierarchy of BDM exceptions, so it's not clear what exactly went wrong.

Sergey, could you please give it another try on the recent ISO?

Hi, Roman.

Unfortunately, I have no that environment, but have tried with other setup. Problem is reproduced

MOS 8.0, ISO #361

Environment:
    * 50 baremetal nodes
    * Ceph *is not* used
        - Cinder LVM over iSCSI for volumes is enabled, rest of checkboxes are disabled
    * Ceilometer, Murano and Sahara *are* installed
    * Each node has 32142MB RAM, 12 CPU

So as you can see, environment is similar but Ceph is not used. I've tried the same usecase as mentioned, and succeed to reproduce:
    * Failed instance is 18807ac1-c130-4c56-bc04-f7b047076e95
    * Volume snapshot is af872626-e0bb-4b00-b9f7-6c5bb0f620e1
    * Snapshot is made from volume 9e165e5c-3ba1-4048-affd-bdfee3059444

Error:
    * Message: Build of instance 18807ac1-c130-4c56-bc04-f7b047076e95 aborted: Block Device Mapping is Invalid.
    * Code: 500
    * Details:
File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1905, in _do_build_and_run_instance filter_properties) File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2025, in _build_and_run_instance 'create.error', fault=e) File "/usr/lib/python2.7/dist-packages/oslo_utils/excutils.py", line 195, in __exit__ six.reraise(self.type_, self.value, self.tb) File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 1996, in _build_and_run_instance block_device_mapping) as resources: File "/usr/lib/python2.7/contextlib.py", line 17, in __enter__ return self.gen.next() File "/usr/lib/python2.7/dist-packages/nova/compute/manager.py", line 2143, in _build_resources reason=e.format_message())
    * Created Jan. 11, 2016, 3:48 p.m.

I cannot create diagnostic snapshot due to https://bugs.launchpad.net/fuel/+bug/1529182 so I've gathered all possible logs (not *.gz). Please find them here:
https://drive.google.com/a/mirantis.com/file/d/0B9tzODpFABxkS3h2ZmN1R0ZVQXc/view?usp=sharing

Versions in ISO #361:

root@node-4:~# dpkg -l | grep -E "nova|cinder" | awk '{print $2,"\t",$3}'
cinder-api 2:7.0.1-1~u14.04+mos7
cinder-common 2:7.0.1-1~u14.04+mos7
cinder-scheduler 2:7.0.1-1~u14.04+mos7
nova-api 2:12.0.0-1~u14.04+mos19
nova-cert 2:12.0.0-1~u14.04+mos19
nova-common 2:12.0.0-1~u14.04+mos19
nova-conductor 2:12.0.0-1~u14.04+mos19
nova-consoleauth 2:12.0.0-1~u14.04+mos19
nova-consoleproxy 2:12.0.0-1~u14.04+mos19
nova-objectstore 2:12.0.0-1~u14.04+mos19
nova-scheduler 2:12.0.0-1~u14.04+mos19
python-cinder 2:7.0.1-1~u14.04+mos7
python-cinderclient 1:1.4.0-1~u14.04+mos2
python-nova 2:12.0.0-1~u14.04+mos19
python-novaclient 2:2.30.2-1~u14.04+mos3

Looks like #1533197 is a more general case