Bug 953546
| Summary: | engine: vm's status remain up although hosts are non-responsive | ||||||
|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Dafna Ron <dron> | ||||
| Component: | ovirt-engine | Assignee: | Nobody's working on this, feel free to take it <nobody> | ||||
| Status: | CLOSED DUPLICATE | QA Contact: | |||||
| Severity: | high | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 3.2.0 | CC: | acathrow, dyasny, iheim, lpeer, ofrenkel, Rhev-m-bugs, yeylon, ykaul | ||||
| Target Milestone: | --- | Keywords: | Regression | ||||
| Target Release: | 3.2.0 | ||||||
| Hardware: | x86_64 | ||||||
| OS: | Linux | ||||||
| Whiteboard: | virt | ||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-04-22 12:21:03 UTC | Type: | Bug | ||||
| Regression: | --- | Mount Type: | --- | ||||
| Documentation: | --- | CRM: | |||||
| Verified Versions: | Category: | --- | |||||
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||
| Embargoed: | |||||||
| Attachments: |
|
||||||
*** This bug has been marked as a duplicate of bug 921521 *** |
Created attachment 737298 [details] logs Description of problem: I blocked connectivity to my hosts from rhevm using iptables and the vm's status stay up. logs show that VdsNotRespondingTreatment fails to run with CanDoAction: 2013-04-18 14:12:04,873 WARN [org.ovirt.engine.core.bll.VdsNotRespondingTreatmentCommand] (pool-4-thread-43) [65a6fc23] CanDoAction of action VdsNotRespondingTreatment failed. Reasons:VDS_FENCE_DISABLED Version-Release number of selected component (if applicable): sf13.1 How reproducible: 100% Steps to Reproduce: 1. don't setup fence on your hosts 2. block connectivity from the rhevm to the hosts using iptables 3. Actual results: vm's statsu stay up although hosts are non-responsive Expected results: vm's status should become unknown. Additional info: logs db is showing status up: engine=# SELECT status from vm_dynamic ; status -------- 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 1 (20 rows)