[Update] Volume can not be created / listed after patching

[Tatyanka]

Steps to reproduce:
1. Deploy HA env on Centos with nova and cinder (5.0-26-2014.1). Run ostf to be sure that os works
2. Upgrade master node to next version({"build_id": "2014-08-14_12-04-35", "ostf_sha": "d2a894d228c1f3c22595a77f04b1e00d09d8e463", "build_number": "437", "auth_required": true, "api": "1.0", "nailgun_sha": "b5bdd19c2dbeb26ce3bd88270d09f5e7541a3aea", "production": "docker", "fuelmain_sha": "9f327045cdd72d406d89063393a499635be5e3d4", "astute_sha": "b52910642d6de941444901b0f20e95ebbcb2b2e9", "feature_groups": ["mirantis"], "release": "5.1", "fuellib_sha": "4b085bfbf7be973f0aa29d9d5e4f3ebd5bf789a1"})

3. Run environmnet update to release 5.0.2-2014.1.1
4. Run ostf

Expected result:
OSTF tests are passed

Actual result:
Volume service is not operational . I can not retrieve volume limits. volume list, can not create volume
http://paste.openstack.org/show/95064/

ostf for volumes ffailed too.
controller -> node 16

[Vladimir Kuklin (vkuklin)]

might be fixed by oslo.messaging patch

[Ivan Kolodyazhny (e0ne)]

Duplicate to bug #1355792

[Tatyanka (tatyana-leontovich)]

Reproduced from time to time

[Ivan Kolodyazhny (e0ne)]

Cinder failed to connect to RabbitMQ. It's a oslo.messaging bug

[Dmitry Mescheryakov (dmitrymex)]

Tatyana, please provide us an environment with repro. We need to diagnose the problem with rabbit. Once you get it, ping me and I will find people who can investigate.

[Tatyanka (tatyana-leontovich)]

I ping you, but you are like me :) Ivan K looked at the 2 env with such problems. Is it enaught?

[Tatyanka (tatyana-leontovich)]

I've updateed python-ciner client on controller - restart cinder-api and cinder scheduler - volumes successfully listed/ created/attached

[Tatyanka (tatyana-leontovich)]

So I belive this issue related to the https://bugs.launchpad.net/mos/+bug/1359705

[Dmitry Mescheryakov (dmitrymex)]

Talked with Tatyana and Sergey Melikyan. We think that fixing https://bugs.launchpad.net/mos/+bug/1356942 should fix that problem as well. Need to try reproduce that issue once 1356942 is fixed.

[Dmitry Mescheryakov (dmitrymex)]

Oops, just noticed I gave link to the wrong bug. We actually think that fixing https://bugs.launchpad.net/mos/+bug/1359705 should fix current problem.

[Dmitry Mescheryakov (dmitrymex)]

The fix to bug 1359705 will be in ISO starting from build #487. Tatyana, please reverify bug on that ISO.

[Tatyanka (tatyana-leontovich)]

Hey :) if you need issue verification, you should use fix commited :)

[Dmitry Mescheryakov (dmitrymex)]

Tatyana, ok, did it

[Dmitry Mescheryakov (dmitrymex)]

The #487 does not contain the fix. I misunderstood 5.1 upgrade tarball build sequence. I will post here 5.1 build number which includes the fix once it is made.

[Dmitry Mescheryakov (dmitrymex)]

Ok, if my estimation is right, build #491 must have the fix.