Volumes are stuck in creating state after reboot primary controller

Bug #1355792 reported by Andrey Sledzinskiy
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Mirantis OpenStack
Fix Committed
Critical
Ivan Kolodyazhny
5.0.x
Won't Fix
Critical
Andrey Sledzinskiy
5.1.x
Fix Committed
Critical
Ivan Kolodyazhny

Bug Description

{

    "build_id": "2014-08-11_12-45-06",
    "mirantis": "yes",
    "build_number": "169",
    "ostf_sha": "09b6bccf7d476771ac859bb3c76c9ebec9da9e1f",
    "nailgun_sha": "04ada3cd7ef14f6741a05fd5d6690260f9198095",
    "production": "docker",
    "api": "1.0",
    "fuelmain_sha": "43374c706b4fdce28aeb4ef11e69a53f41646740",
    "astute_sha": "6db5f5031b74e67b92fcac1f7998eaa296d68025",
    "release": "5.0.1",
    "fuellib_sha": "a31dbac8fff9cf6bc4cd0d23459670e34b27a9ab"

}

Steps:
1. Create next cluster - Centos, HA, Neutron GRE, Cinder for volumes, 3 controllers, 1 compute, 1 cinder
2. Deploy cluster
3. After successfull deployment make reboot of primary controller
4. Wait for half an hour
5. Try to create volume

Expected - volume can be created
Actual - volume stuck in creation state

Errors in cinder-volume.log on cinder node (node-15):
oslo.messaging._drivers.impl_rabbit [-] Failed to publish message to topic 'cinder-scheduler': (0, 0): (320) CONNECTION_FORCED - broker forced connection closure with reason 'shutdown'

Errors in nova-compute.log on compute node (node-14):
oslo.messaging._drivers.impl_rabbit [-] Failed to publish message to topic 'conductor': [Errno 32] Broken pipe

Logs are attached

Logs are attached

Revision history for this message
Andrey Sledzinskiy (asledzinskiy) wrote :
affects: oslo.messaging → mos
Changed in mos:
importance: Undecided → High
assignee: nobody → MOS Oslo (mos-oslo)
milestone: none → 5.1
milestone: 5.1 → 5.0.1
Changed in mos:
assignee: MOS Oslo (mos-oslo) → Ivan Kolodyazhny (e0ne)
importance: High → Medium
importance: Medium → High
Ivan Kolodyazhny (e0ne)
tags: added: cinder
Ivan Kolodyazhny (e0ne)
Changed in mos:
status: New → Confirmed
status: Confirmed → In Progress
Revision history for this message
OSCI Robot (oscirobot) wrote :
Revision history for this message
OSCI Robot (oscirobot) wrote :
Changed in mos:
importance: High → Medium
milestone: 5.0.1 → 5.0.2
tags: added: release-notes
Revision history for this message
OSCI Robot (oscirobot) wrote :
Revision history for this message
Meg McRoberts (dreidellhasa) wrote :

For the Release Notes, what do they do if this happens?

Revision history for this message
Ivan Kolodyazhny (e0ne) wrote :

Here is patch to fix this problem: http://paste.openstack.org/show/95051/

Revision history for this message
Dmitry Borodaenko (angdraug) wrote :

Workaround is to restart cinder services, force-delete and re-create the affected volumes.

Revision history for this message
OSCI Robot (oscirobot) wrote :

Package cinder has been built from changeset: http://gerrit.mirantis.com/20456
RPM Repository URL: http://osci-obs.vm.mirantis.net:82/centos-fuel-5.1-stable/centos

Revision history for this message
OSCI Robot (oscirobot) wrote :

Package cinder has been built from changeset: http://gerrit.mirantis.com/20456
DEB Repository URL: http://osci-obs.vm.mirantis.net:82/ubuntu-fuel-5.1-stable/ubuntu

Revision history for this message
Dmitry Mescheryakov (dmitrymex) wrote :

Please port this change to MOS 5.0.2

Revision history for this message
OSCI Robot (oscirobot) wrote :
Revision history for this message
OSCI Robot (oscirobot) wrote :
Revision history for this message
OSCI Robot (oscirobot) wrote :

Package cinder has been built from changeset: http://gerrit.mirantis.com/20681
RPM Repository URL: http://osci-obs.vm.mirantis.net:82/centos-fuel-5.0.2-stable/centos

Revision history for this message
OSCI Robot (oscirobot) wrote :

Package cinder has been built from changeset: http://gerrit.mirantis.com/20681
DEB Repository URL: http://osci-obs.vm.mirantis.net:82/ubuntu-fuel-5.0.2-stable/ubuntu

Revision history for this message
Tatyanka (tatyana-leontovich) wrote :

Set to critical according to fail a lot of cases of patching feature

Revision history for this message
Tatyanka (tatyana-leontovich) wrote :

Still reproduced on {"build_id": "2014-08-20_02-01-17", "ostf_sha": "c6ecd0137b5d7c1576fa65baef0fc70f9a150daa", "build_number": "459", "auth_required": true, "api": "1.0", "nailgun_sha": "36d27ff737b361f92093986d061bbfc1670bee45", "production": "docker", "fuelmain_sha": "365fc0bfe9d5e4ce38101d9158f66347bf32c310", "astute_sha": "efe3cb3668b9079e68fb1534fd4649ac45a344e1", "feature_groups": ["mirantis"], "release": "5.1", "fuellib_sha": "fa23adb05c58fdad5011a3ad806467eb3d883217"} Package cinder has changes

http://paste.openstack.org/show/97798/

Revision history for this message
Dmitry Mescheryakov (dmitrymex) wrote :

Clarification from chat with Tatyana: the issue was reproduced on 5.0.2

Revision history for this message
Ivan Kolodyazhny (e0ne) wrote :

Works on ISO:
{
build_id: "2014-08-22_14-59-17",
ostf_sha: "907f25f8fad39b177bf6a66fba9785afa7dd8008",
build_number: "469",
auth_required: true,
api: "1.0",
nailgun_sha: "e9dd053fce12908b5a5a404435ce2e8200450a23",
production: "docker",
fuelmain_sha: "5a7df58786db7962a1774b5be3611c4e7543015d",
astute_sha: "ac520b09525af4551e730b1c1f78170fefaf3cb8",
feature_groups: [
"mirantis"
],
release: "5.1",
fuellib_sha: "bddba1e854a6b0350e844a0baad50816d3cc8e28"
}

Unable to reproduce an issue with provided steps

Revision history for this message
Tatyanka (tatyana-leontovich) wrote :

Ivan you closes this one issue https://bugs.launchpad.net/fuel/+bug/1356942 as duplicate of this , could you confirm that it is worked too?

Revision history for this message
Ivan Kolodyazhny (e0ne) wrote :

Andrey, please, confirm bug as fixes with the latest oslo.messaging lib or provide more detailed steps to reproduce

Revision history for this message
Dmitry Mescheryakov (dmitrymex) wrote :

Andrey, for your reference, the fix for oslo.messaging will appear in 5.0.2 only after https://bugs.launchpad.net/mos/+bug/1359705 is fixed

Revision history for this message
Dmitry Mescheryakov (dmitrymex) wrote :

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

Revision history for this message
Dmitry Mescheryakov (dmitrymex) wrote :

Also the bug was wrongly moved to incomplete in release 5.1. Actually the fix is committed there and no problems were observed so far.

Revision history for this message
Dmitry Mescheryakov (dmitrymex) wrote :

Move to 'fix committed' to indicate readiness to be tested by QA folks, as suggested by Tatyana.

Revision history for this message
Dmitry Mescheryakov (dmitrymex) wrote :

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.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.