Red Hat Bugzilla – Bug 977689
After enable concurrent option under host power management fencing begin failed
Last modified: 2016-02-10 14:06:47 EST
Created attachment 764960 [details]
Description of problem:
After enable concurrent option under host power management fencing stop working
Version-Release number of selected component (if applicable):
Add host, add primary and secondary agents of power management, check via test button if agents defined correct. Check concurrent option and try to restart host.
Steps to Reproduce:
1. See above
Host not restarted.
Error messages in events:
Failed to restart Host your_host, (User: admin@internal).
Failed to stop Host your_host, (User: admin@internal)
Created attachment 764961 [details]
rhevm version sf18
Restart is performed as stop, wait for status off, start, wait for status on.
Please verify that your log includes this sequence in the engine side.
Created attachment 767037 [details]
Full vdsm log
Created attachment 767081 [details]
Full engine log
fixed in commit: 9869244
Can't verified bug because this bug https://bugzilla.redhat.com/show_bug.cgi?id=982266, have host just with power managements types apc_snmp and ipmilan and I need host with two power management.
Check with the same power management as first and second pm's with concurrent enabled, fence worked fine.(No have hosts with two different power managements of same type)
Verified on is9.1
This bug is currently attached to errata RHEA-2013:15231. If this change is not to be documented in the text for this errata please either remove it from the errata, set the requires_doc_text flag to minus (-), or leave a "Doc Text" value of "--no tech note required" if you do not have permission to alter the flag.
Otherwise to aid in the development of relevant and accurate release documentation, please fill out the "Doc Text" field above with these four (4) pieces of information:
* Cause: What actions or circumstances cause this bug to present.
* Consequence: What happens when the bug presents.
* Fix: What was done to fix the bug.
* Result: What now happens when the actions or circumstances above occur. (NB: this is not the same as 'the bug doesn't present anymore')
Once filled out, please set the "Doc Type" field to the appropriate value for the type of change made and submit your edits to the bug.
For further details on the Cause, Consequence, Fix, Result format please refer to:
Thanks in advance.
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.
For information on the advisory, and where to find the updated
files, follow the link below.
If the solution does not work for you, open a new bug report.