Info-bug: Failed to attach volume

[Egor Kotko]

Further information about this bug is here:
https://bugs.launchpad.net/nova/+bug/1288210

Steps to reproduce:
1. Create env:
Centos, multinode, 1Controller, 1 Compute, 1 Cinder, 2 Cephs, Neutron GRE, Cinder LVM, Ceph images
2. Create Instance(from image)
3. Create empty volume
4. Attach volume to instance

Actual result:
Status of volume Available, volume in not attached

Expected result:
Status of volumes should be in-use, volume is attached

[Tatyanka (tatyana-leontovich)]

can not reproduce on 271-4.1.1 for the same configurations

[Tatyanka (tatyana-leontovich)]

Does anybody reproduce it last time? Seems we can close this issue )

[Andrey Shestakov (ashestakov)]

Reproduced in 5.0
Also reproduced in Ubuntu in HA mode

[Bogdan Dobrelya (bogdando)]

There are 2 ceph nodes and 1 cinder lvm node in a roles list, the question is which backend was used for cinder volumes for the reproduced case?

[Egor Kotko (ykotko)]

In my case I have used Ceph for images and Cinder volume backend.

[Andrey Shestakov (ashestakov)]

I have this problem even without Ceph, just cinder iscsi

[Tatyanka (tatyana-leontovich)]

verified {"build_id": "2014-06-04_09-16-08", "mirantis": "yes", "build_number": "341", "nailgun_sha": "a828d6b7610f872980d5a2113774f1cda6f6810b", "ostf_sha": "c959aa55f83fe2555cf2d382559271c7a9b17467", "fuelmain_sha": "7ed0f85acc0bab4b9157703a618b8cc9fd7de3e1", "astute_sha": "55df06b2e84fa5d71a1cc0e78dbccab5db29d968", "release": "4.1B", "fuellib_sha": "0e96fc5a340cd57f75c454ea8536471379299494"}

[Timur Nurlygayanov (tnurlygayanov)]

Andrey Shestakov confirmed that this issue reproduced on Fuel 5.x (from master).
Need to investigate the root of this problem and fix it.

[Timur Nurlygayanov (tnurlygayanov)]

Andrey Shestakov can provide more details

[Timur Nurlygayanov (tnurlygayanov)]

Ivan, could you please check this issue and fix it? Looks like the root of this problem in Cinder.

Please, also, note that we have some 'magic' timeout, after this timeout all works fine, but if we will do this imediatly after the OpenStack deployment this issue will reproduced.

[Nastya Urlapova (aurlapova)]

Timur, please provide more debug info than man name.

[Timur Nurlygayanov (tnurlygayanov)]

Not reproduced on my environment, looks like Andrey already removed the environment with this issue. So, bug marked as invalid and we will retest it again - if this issue will reproduced, we will update this bug and provide access to the environment.