Bug 1316358 - [HC] vm high availability is not working against a glusterfs storage domain
[HC] vm high availability is not working against a glusterfs storage domain
Status: CLOSED UPSTREAM
Product: Red Hat Enterprise Virtualization Manager
Classification: Red Hat
Component: ovirt-engine (Show other bugs)
3.6.3
x86_64 Linux
medium Severity medium
: ---
: ---
Assigned To: nobody nobody
:
Depends On:
Blocks: Gluster-HC-1 1316692
  Show dependency treegraph
 
Reported: 2016-03-09 22:28 EST by Paul Cuzner
Modified: 2016-03-10 17:25 EST (History)
8 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
: 1316692 (view as bug list)
Environment:
Last Closed: 2016-03-10 17:25:21 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: Gluster
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
engine.log (1.40 MB, application/x-gzip)
2016-03-09 22:28 EST, Paul Cuzner
no flags Details
vdsm log from the host that was powered off during the test (847.06 KB, application/x-gzip)
2016-03-09 22:29 EST, Paul Cuzner
no flags Details

  None (edit)
Description Paul Cuzner 2016-03-09 22:28:07 EST
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
Comment 1 Paul Cuzner 2016-03-09 22:29 EST
Created attachment 1134695 [details]
vdsm log from the host that was powered off during the test
Comment 2 Yaniv Lavi 2016-03-10 04:09:45 EST
If this reproduces on non HC setup, please move it to SLA.
Comment 3 Yaniv Lavi 2016-03-10 17:25:21 EST
We will handle this issue in the upstream bug.

Note You need to log in before you can comment on or make changes to this bug.