Bug 1131411
| Summary: | Fencing with proxy from other_dc is actually performed by a proxy in the same dc | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Retired] oVirt | Reporter: | sefi litmanovich <slitmano> | ||||
| Component: | ovirt-engine-core | Assignee: | Eli Mesika <emesika> | ||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | sefi litmanovich <slitmano> | ||||
| Severity: | unspecified | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.5 | CC: | bugs, ecohen, gklein, iheim, oourfali, rbalakri, s.kieske, yeylon | ||||
| Target Milestone: | --- | ||||||
| Target Release: | 3.5.0 | ||||||
| Hardware: | Unspecified | ||||||
| OS: | Unspecified | ||||||
| Whiteboard: | infra | ||||||
| Fixed In Version: | ovirt-3.5.0_rc2 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2014-10-17 12:28:09 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | Infra | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Bug Depends On: | |||||||
| Bug Blocks: | 1114253 | ||||||
| Attachments: |
|
||||||
Verified with rhevm-3.5.0-0.12.beta.el6ev.noarch according to the use case in the description. oVirt 3.5 has been released and should include the fix for this issue. |
Created attachment 928219 [details] engine and vdsm (HOST1) logs Description of problem: In regards to the new feature enabling fencing using a proxy from another dc: Steps to Reproduce: 1. add other_dc proxy source option through the api. 2. have an engine with 3 hosts - one with pm (HOST_PM) in DC1, Cluster1, another (HOST1) in DC1, Cluster1 and one host (HOST2) in DC2 Cluster2. 3. edit the host with pm, in power management tab provide a working fence agent credentials and choose other_dc as the high priority for proxy source. 4. click the test button to perform a fence STATUS action. (Also tried RESTART action as well) Version-Release number of selected component (if applicable): 3.5 Actual results: the actual fence action is performed by the host in the same dc as host_with_pm. Also a false audit log message is issued: Host HOST1 from other data center was chosen as a proxy to execute Status command on Host HOST_PM. in engine.log you can see all fencing actions were performed by HOST1 an not HOST2, also in HOST1's vdsm.log Expected results: the fence actions are performed by the host in the other dc (HOST2). audit log message is issued: Host HOST2 from other data center was chosen as a proxy to execute Status command on Host HOST_PM. Additional info: