[library] Errors in corosync.log on all of controllers for HA mode

Bug #1331450 reported by Anastasia Palkina
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
Invalid
Medium
Sergii Golovatiuk

Bug Description

"build_id": "2014-06-17_18-06-05",
"mirantis": "yes",
"build_number": "258",
"ostf_sha": "1740b5ce42ea1893f7d3e2c6cc59720bdb77c007",
"nailgun_sha": "057bb88abab1048322ed0ff48d632f8caf146e5a",
"production": "docker",
"api": "1.0",
"fuelmain_sha": "ba9e19a3822d9c1dcda2f4046f2f5e3e6ac505dd",
"astute_sha": "17b1afa5f0dc8f4fca5ed4eb03ec566fbfb5ed19",
"release": "5.1",
"fuellib_sha": "ff050d23d8a845cd097f7aa617285da0ab1894f6"

1. Create new environment (CentOS, HA mode)
2. Choose nova-network
3. Add 3 controllers+cinder, 1 compute
4. Start deployment. It was successful
5. But there are errors in corosync.log on all of controllers (node-1,2,3)

Jun 18 11:12:38 err: [pcmk ] ERROR: process_ais_conf: You have configured a cluster using the Pacemaker plugin for Corosync. The plugin is not supported in this environment and will be removed very soon.
Jun 18 11:12:38 err: [pcmk ] ERROR: process_ais_conf: Please see Chapter 8 of 'Clusters from Scratch' (http://www.clusterlabs.org/doc) for details on using Pacemaker with CMAN

Revision history for this message
Anastasia Palkina (apalkina) wrote :
Changed in fuel:
status: New → Confirmed
importance: Undecided → Low
Revision history for this message
Bogdan Dobrelya (bogdando) wrote :

Issue should be addressed by updating the Pacemaker and Corosync stack

Changed in fuel:
status: Confirmed → Triaged
Dmitry Ilyin (idv1985)
summary: - Errors in corosync.log on all of controllers for HA mode
+ [library] Errors in corosync.log on all of controllers for HA mode
Changed in fuel:
milestone: 5.1 → 6.0
importance: Low → High
Changed in fuel:
assignee: Fuel Library Team (fuel-library) → Sergii Golovatiuk (sgolovatiuk)
milestone: 6.0 → 6.1
Revision history for this message
Sergii Golovatiuk (sgolovatiuk) wrote :

This issue should go away after upgrading Corosync to 2.X. Since we are in feature freeze, corosync 2.x packages will be added to 6.1

Changed in fuel:
importance: High → Medium
Revision history for this message
Sergii Golovatiuk (sgolovatiuk) wrote :

This bug is invalid as we switched to corosync 2.0. I cannot see such warnings anymore.

Changed in fuel:
status: Triaged → Invalid
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.