Bug 1316358
| Summary: | [HC] vm high availability is not working against a glusterfs storage domain | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat Enterprise Virtualization Manager | Reporter: | Paul Cuzner <pcuzner> | ||||||
| Component: | ovirt-engine | Assignee: | Nobody <nobody> | ||||||
| Status: | CLOSED UPSTREAM | QA Contact: | |||||||
| Severity: | medium | Docs Contact: | |||||||
| Priority: | medium | ||||||||
| Version: | 3.6.3 | CC: | gklein, lsurette, rbalakri, Rhev-m-bugs, sabose, yeylon, ykaul, ylavi | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Linux | ||||||||
| Whiteboard: | |||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | |||||||||
| : | 1316692 (view as bug list) | Environment: | |||||||
| Last Closed: | 2016-03-10 22:25:21 UTC | Type: | Bug | ||||||
| Regression: | --- | Mount Type: | --- | ||||||
| Documentation: | --- | CRM: | |||||||
| Verified Versions: | Category: | --- | |||||||
| oVirt Team: | Gluster | RHEL 7.3 requirements from Atomic Host: | |||||||
| Cloudforms Team: | --- | Target Upstream Version: | |||||||
| Embargoed: | |||||||||
| Bug Depends On: | |||||||||
| Bug Blocks: | 1258386, 1316692 | ||||||||
| Attachments: |
|
||||||||
Created attachment 1134695 [details]
vdsm log from the host that was powered off during the test
If this reproduces on non HC setup, please move it to SLA. We will handle this issue in the upstream bug. |
Created attachment 1134694 [details] engine.log Description of problem: While testing a hyperconverged set up, I set vm's to highly available and have defined the fencing agent (idrac7) to the hosts. When a host running vm's is powered off through the DRAC, the vm's do not restart on one of the other nodes. When the host down is detected, the event is shown as "User shutdown from within the guest" - which is not true. Version-Release number of selected component (if applicable): 3.6.3.4-0.1 How reproducible: This is observed each time. Steps to Reproduce: 1. Hyperconverged setup with RHEV 3.6 and Gluster 3.7 2. set vm's to be highly available 3. power off a host running a vm that is tagged as highly available 4. confirm that a) message shows that the engine believes the vm to have shut itself down b) vm is not restarted Actual results: VM's marked as highly available do NOT get restarted on the other nodes in the cluster Expected results: VM's with the highly available attribute should be restarted. Additional info: This issue was reported informally to Doron Fediuck and Roy Golan a couple of weeks ago. Attaching engine.log and vdsm.log from the node shutdown for analysis