[system tests 4.1] Pacemaker status failed with 'unknown error'
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
Fuel for OpenStack |
Fix Released
|
Medium
|
Andrey Sledzinskiy |
Bug Description
Bug is reproduced on {"build_id": "2014-04-
Steps:
1. Create next cluster - HA, Centos, KVM, Flat Nova network without tagging, Cinder LVM
2. Add 3 controlles, 2 compute nodes
3. Deploy cluster
4. After successful deploy ssh to controller and execute 'crm_mon -1'
Actual result :
3 Nodes configured, 3 expected votes
9 Resources configured
Online: [ node-1.
vip__managemen
vip__public_old (ocf::mirantis:
Clone Set: clone_p_haproxy [p_haproxy]
Started: [ node-1.
Clone Set: clone_p_mysql [p_mysql]
Started: [ node-1.
openstack-
Failed actions:
vip_
, queued=0ms, exec=0ms
): unknown error
vip_
, queued=0ms, exec=0ms
): unknown error
Logs are attached
Changed in fuel: | |
milestone: | 4.1.1 → 5.0 |
tags: | added: backports-4.1.1 |
Changed in fuel: | |
assignee: | nobody → Fuel Library Team (fuel-library) |
Changed in fuel: | |
status: | New → Confirmed |
report shows that some shell commands used for ipaddr resources monitoring, usually these are simple calls of ifconfig or `ip` commands. it is expected behaviour if these commands fail. this should not usually happen, but pacemaker should handle this situation and everything should work ok. so, please provide info, which tests have failed or which functionality is broken.