Activity log for bug #1436812

Date Who What changed Old value New value Message
2015-03-26 11:55:44 Alexey Khivin bug added bug
2015-03-26 12:27:57 Alexey Khivin bug added subscriber Dmitry Savenkov
2015-03-26 12:30:39 Alexey Khivin summary Entire RabbitMQ cluster downtime when primary controller goes down Full RabbitMQ cluster failure when primary controller goes down
2015-03-26 14:24:44 Davanum Srinivas (DIMS) bug added subscriber Davanum Srinivas (DIMS)
2015-03-26 16:13:57 Stanislaw Bogatkin fuel: importance Critical High
2015-03-26 16:14:18 Stanislaw Bogatkin fuel: status New Confirmed
2015-03-27 10:57:39 Bogdan Dobrelya marked as duplicate 1435254
2015-03-27 10:58:38 Bogdan Dobrelya removed duplicate marker 1435254
2015-03-27 10:58:44 Bogdan Dobrelya fuel: milestone 7.0
2015-03-31 09:11:09 Bogdan Dobrelya fuel: status Confirmed Won't Fix
2015-03-31 13:11:31 Bogdan Dobrelya nominated for series fuel/6.1.x
2015-03-31 13:11:31 Bogdan Dobrelya bug task added fuel/6.1.x
2015-03-31 13:11:39 Bogdan Dobrelya fuel/6.1.x: status Won't Fix In Progress
2015-03-31 13:11:42 Bogdan Dobrelya fuel/6.1.x: milestone 7.0 6.1
2015-03-31 13:13:03 Bogdan Dobrelya bug task deleted fuel/6.1.x
2015-05-15 13:34:46 Bogdan Dobrelya summary Full RabbitMQ cluster failure when primary controller goes down Full RabbitMQ cluster failure when the master of rabbit multi-state resource goes down
2015-05-15 13:35:55 Bogdan Dobrelya description Multinode with HA with 3 controllers Steps to reproduce 1) find primary controller (crm status) 2) On the other two controllers start watch "rabbitmqctl eval 'rabbit_misc:which_applications().' |grep rabbit," to see whats happening with RabbitMQ cluster and rabbit application. You should see the line {rabbit,"RabbitMQ","3.3.5"}, 3) Turn off the primary controller and see whats happening with other two controllers Because of currrent HA implementation you will see that rabbitmqctl could not connect to the node something like that Error: unable to connect to node 'rabbit@node-10': nodedown or line with rabbitmq application could disappear The normal behaviour I believe should be No disconnection on two others controllers and no full cluster failover when primary controller goes down Also in the https://bugs.launchpad.net/fuel/+bug/1435250 noted 3) destroy the master, node-3 Expected: new master election, failover with full downtime - no nodes can process AMQP connections I think It should be improved [root@fuel ~]# fuel --f DEPRECATION WARNING: file /etc/fuel/client/config.yaml is found and will be used as a source for settings. However, it deprecated and will not be used by default in the ongoing version of python-fuelclient. api: '1.0' astute_sha: 4a117a1ca6bdcc34fe4d086959ace1a6d18eeca9 auth_required: true build_id: 2015-03-23_15-29-20 build_number: '218' feature_groups: - mirantis fuellib_sha: a0265ae47bb2307a6967a3f1dd06fe222c561265 fuelmain_sha: a05ab877af31924585c81081f45305700961458e nailgun_sha: 7c100f47450ea1a910e19fa09f78d586cb2bc0d3 ostf_sha: a4cf5f218c6aea98105b10c97a4aed8115c15867 production: docker python-fuelclient_sha: 3624051242c83fdbdd1df9a0e466797c06b75043 release: '6.1' release_versions: 2014.2-6.1: VERSION: api: '1.0' astute_sha: 4a117a1ca6bdcc34fe4d086959ace1a6d18eeca9 build_id: 2015-03-23_15-29-20 build_number: '218' feature_groups: - mirantis fuellib_sha: a0265ae47bb2307a6967a3f1dd06fe222c561265 fuelmain_sha: a05ab877af31924585c81081f45305700961458e nailgun_sha: 7c100f47450ea1a910e19fa09f78d586cb2bc0d3 ostf_sha: a4cf5f218c6aea98105b10c97a4aed8115c15867 production: docker python-fuelclient_sha: 3624051242c83fdbdd1df9a0e466797c06b75043 release: '6.1' Multinode with HA with 3 controllers Steps to reproduce 1) find the master of rabbitmq multistate-resource (crm status) 2) On the other two controllers start watch "rabbitmqctl eval 'rabbit_misc:which_applications().' |grep rabbit," to see whats happening with RabbitMQ cluster and rabbit application. You should see the line {rabbit,"RabbitMQ","3.3.5"}, 3) Turn off the primary controller and see whats happening with other two controllers Because of currrent HA implementation you will see that rabbitmqctl could not connect to the node something like that Error: unable to connect to node 'rabbit@node-10': nodedown or line with rabbitmq application could disappear The normal behaviour I believe should be No disconnection on two others controllers and no full cluster failover when primary controller goes down Also in the https://bugs.launchpad.net/fuel/+bug/1435250 noted 3) destroy the master, node-3 Expected: new master election, failover with full downtime - no nodes can process AMQP connections I think It should be improved [root@fuel ~]# fuel --f DEPRECATION WARNING: file /etc/fuel/client/config.yaml is found and will be used as a source for settings. However, it deprecated and will not be used by default in the ongoing version of python-fuelclient. api: '1.0' astute_sha: 4a117a1ca6bdcc34fe4d086959ace1a6d18eeca9 auth_required: true build_id: 2015-03-23_15-29-20 build_number: '218' feature_groups: - mirantis fuellib_sha: a0265ae47bb2307a6967a3f1dd06fe222c561265 fuelmain_sha: a05ab877af31924585c81081f45305700961458e nailgun_sha: 7c100f47450ea1a910e19fa09f78d586cb2bc0d3 ostf_sha: a4cf5f218c6aea98105b10c97a4aed8115c15867 production: docker python-fuelclient_sha: 3624051242c83fdbdd1df9a0e466797c06b75043 release: '6.1' release_versions:   2014.2-6.1:     VERSION:       api: '1.0'       astute_sha: 4a117a1ca6bdcc34fe4d086959ace1a6d18eeca9       build_id: 2015-03-23_15-29-20       build_number: '218'       feature_groups:       - mirantis       fuellib_sha: a0265ae47bb2307a6967a3f1dd06fe222c561265       fuelmain_sha: a05ab877af31924585c81081f45305700961458e       nailgun_sha: 7c100f47450ea1a910e19fa09f78d586cb2bc0d3       ostf_sha: a4cf5f218c6aea98105b10c97a4aed8115c15867       production: docker       python-fuelclient_sha: 3624051242c83fdbdd1df9a0e466797c06b75043       release: '6.1'
2015-05-15 23:50:46 Dmitry Borodaenko fuel: status Won't Fix Confirmed
2015-05-15 23:50:51 Dmitry Borodaenko fuel: milestone 6.1 5.1.1-updates
2015-05-15 23:50:59 Dmitry Borodaenko fuel: milestone 5.1.1-updates 7.0
2015-05-16 21:06:39 Vladimir Kuklin fuel: status Confirmed Invalid
2015-05-17 07:14:40 Bogdan Dobrelya fuel: status Invalid Won't Fix
2015-05-19 16:12:05 Mike Scherbakov fuel: status Won't Fix Confirmed
2015-05-19 19:06:30 Vitaly Sedelnik nominated for series fuel/6.1.x
2015-05-19 19:06:30 Vitaly Sedelnik bug task added fuel/6.1.x
2015-05-19 19:07:09 Vitaly Sedelnik nominated for series fuel/7.0.x
2015-05-19 19:07:09 Vitaly Sedelnik bug task added fuel/7.0.x
2015-05-19 19:07:16 Vitaly Sedelnik fuel/7.0.x: status New Confirmed
2015-05-19 19:07:19 Vitaly Sedelnik fuel/7.0.x: importance Undecided High
2015-05-19 19:07:29 Vitaly Sedelnik fuel/7.0.x: assignee Fuel Library Team (fuel-library)
2015-05-19 19:07:37 Vitaly Sedelnik fuel/7.0.x: milestone 7.0
2015-05-19 19:07:43 Vitaly Sedelnik fuel/6.1.x: milestone 7.0 6.1.1
2015-05-19 19:07:54 Vitaly Sedelnik fuel/6.1.x: assignee Fuel Library Team (fuel-library) MOS Sustaining (mos-sustaining)
2015-05-22 15:12:00 OpenStack Infra fuel: status Confirmed In Progress
2015-05-22 15:12:00 OpenStack Infra fuel: assignee MOS Sustaining (mos-sustaining) Bogdan Dobrelya (bogdando)
2015-05-23 01:44:24 OpenStack Infra fuel: assignee Bogdan Dobrelya (bogdando) Vladimir Kuklin (vkuklin)
2015-05-25 07:46:24 Bogdan Dobrelya fuel/6.1.x: assignee Vladimir Kuklin (vkuklin) Bogdan Dobrelya (bogdando)
2015-05-25 10:23:54 Bogdan Dobrelya fuel/6.1.x: milestone 6.1.1 6.1
2015-05-25 15:03:05 OpenStack Infra fuel: status In Progress Fix Committed
2015-05-26 11:12:40 Bogdan Dobrelya nominated for series fuel/6.0.x
2015-05-26 11:12:40 Bogdan Dobrelya bug task added fuel/6.0.x
2015-05-26 11:12:40 Bogdan Dobrelya nominated for series fuel/5.1.x
2015-05-26 11:12:40 Bogdan Dobrelya bug task added fuel/5.1.x
2015-05-26 11:12:49 Bogdan Dobrelya bug task deleted fuel/7.0.x
2015-05-26 11:12:56 Bogdan Dobrelya fuel/6.0.x: status New Triaged
2015-05-26 11:12:58 Bogdan Dobrelya fuel/5.1.x: status New Triaged
2015-05-26 11:13:01 Bogdan Dobrelya fuel/6.0.x: importance Undecided High
2015-05-26 11:13:03 Bogdan Dobrelya fuel/5.1.x: importance Undecided High
2015-05-26 11:13:09 Bogdan Dobrelya fuel/6.0.x: assignee Fuel Library Team (fuel-library)
2015-05-26 11:13:14 Bogdan Dobrelya fuel/5.1.x: assignee Fuel Library Team (fuel-library)
2015-05-26 11:13:16 Bogdan Dobrelya fuel/5.1.x: milestone 5.1.2
2015-05-26 11:13:20 Bogdan Dobrelya fuel/6.0.x: milestone 6.0.1
2015-05-28 12:24:29 Sergey Novikov tags ha rabbitmq ha on-verification rabbitmq
2015-05-29 14:16:26 Sergey Novikov tags ha on-verification rabbitmq ha rabbitmq
2015-05-29 14:16:32 Sergey Novikov fuel/6.1.x: status Fix Committed Fix Released
2015-07-13 10:13:43 Bogdan Dobrelya fuel/5.1.x: assignee Fuel Library Team (fuel-library) MOS Sustaining (mos-sustaining)
2015-07-13 10:13:51 Bogdan Dobrelya fuel/6.0.x: assignee Fuel Library Team (fuel-library) MOS Sustaining (mos-sustaining)
2015-10-26 11:27:48 Vitaly Sedelnik fuel/5.1.x: assignee MOS Maintenance (mos-maintenance) Denis Meltsaykin (dmeltsaykin)
2015-10-26 11:27:54 Vitaly Sedelnik fuel/6.0.x: assignee MOS Maintenance (mos-maintenance) Denis Meltsaykin (dmeltsaykin)
2015-10-26 11:27:57 Vitaly Sedelnik fuel/5.1.x: milestone 5.1.1-updates 5.1.1-mu-2
2015-10-26 11:28:01 Vitaly Sedelnik fuel/6.0.x: milestone 6.0-updates 6.0-mu-7
2015-10-26 13:43:16 Denis Meltsaykin fuel/6.0.x: status Triaged Won't Fix
2015-10-26 13:43:18 Denis Meltsaykin fuel/5.1.x: status Triaged Won't Fix
2015-10-26 15:07:57 Vitaly Sedelnik fuel/5.1.x: milestone 5.1.1-mu-2 5.1.1-updates
2015-10-26 15:07:59 Vitaly Sedelnik fuel/6.0.x: milestone 6.0-mu-7 6.0-updates