Bug 441697 - fence_xvm doesn't work from within a VM
fence_xvm doesn't work from within a VM
Status: CLOSED NOTABUG
Product: Red Hat Enterprise Linux 5
Classification: Red Hat
Component: cman (Show other bugs)
5.1
All Linux
low Severity low
: rc
: ---
Assigned To: Lon Hohberger
GFS Bugs
:
Depends On:
Blocks:
  Show dependency treegraph
 
Reported: 2008-04-09 11:14 EDT by Thorsten Scherf
Modified: 2009-04-16 18:56 EDT (History)
2 users (show)

See Also:
Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of:
Environment:
Last Closed: 2008-04-09 13:24:39 EDT
Type: ---
Regression: ---
Mount Type: ---
Documentation: ---
CRM:
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---


Attachments (Terms of Use)
cluster.conf-dom0 (1.37 KB, application/octet-stream)
2008-04-09 11:14 EDT, Thorsten Scherf
no flags Details
cluster.conf-domU (1.37 KB, text/plain)
2008-04-09 11:16 EDT, Thorsten Scherf
no flags Details
cluster.conf-dom0 (450 bytes, text/plain)
2008-04-09 11:17 EDT, Thorsten Scherf
no flags Details

  None (edit)
Description Thorsten Scherf 2008-04-09 11:14:51 EDT
Description of problem:
When I call fence_xvm within a VM, it doesn't work. It says it was sucessful,
but the node supposed to fence is still online:
[root@c10n2 ~]# fence_xvm -d -H node3
-- args @ 0xbff6c190 --
  args->addr = 225.0.0.12
  args->domain = node3
  args->key_file = /etc/cluster/fence_xvm.key
  args->op = 2
  args->hash = 2
  args->auth = 2
  args->port = 1229
  args->family = 2
  args->timeout = 30
  args->retr_time = 20
  args->flags = 0
  args->debug = 1
-- end args --
Remote: Operation was successful

when I do exactly the same from the dom0 node, it works and the node is fenced:

[root@c10n5 ~]# fence_xvm -d -H node3
-- args @ 0xbfb1f520 --
  args->addr = 225.0.0.12
  args->domain = node3
  args->key_file = /etc/cluster/fence_xvm.key
  args->op = 2
  args->hash = 2
  args->auth = 2
  args->port = 1229
  args->family = 2
  args->timeout = 30
  args->retr_time = 20
  args->flags = 0
  args->debug = 1
-- end args --
Remote: Operation was successful

cluster.conf files attched.

Version-Release number of selected component (if applicable):
cman-2.0.73-1.el5, also testet with newer packages, same problem

How reproducible:
call fence_xvm

Steps to Reproduce:
1.
2.
3.
  
Actual results:


Expected results:


Additional info:
Comment 1 Thorsten Scherf 2008-04-09 11:14:51 EDT
Created attachment 301826 [details]
cluster.conf-dom0
Comment 2 Thorsten Scherf 2008-04-09 11:16:18 EDT
Created attachment 301827 [details]
cluster.conf-domU
Comment 3 Thorsten Scherf 2008-04-09 11:17:27 EDT
Created attachment 301828 [details]
cluster.conf-dom0
Comment 4 Lon Hohberger 2008-04-09 11:28:50 EDT
Could you run:

fence_xvmd -fdddd 

...in dom0, reproduce, and paste dom0's output as well?  There's a chance you're
reusing a key file (or your key file is empty).
Comment 5 Lon Hohberger 2008-04-09 11:30:32 EDT
Also, verify that "name=X" lines in /etc/sysconfig/node[123] are node[123]
accordingly, and that xm list shows the names to be the same.
Comment 6 Lon Hohberger 2008-04-09 11:33:02 EDT
Er, /etc/xen/node[123]

Comment 7 Thorsten Scherf 2008-04-09 13:18:16 EDT
                        
looks like the machines using a wrong key?


[root@c10n5 ~]# fence_xvmd -fdddd 
Debugging threshold is now 4
-- args @ 0xbf924b4c --
  args->addr = 225.0.0.12
  args->domain = (null)
  args->key_file = /etc/cluster/fence_xvm.key
  args->op = 2
  args->hash = 2
  args->auth = 2
  args->port = 1229
  args->family = 2
  args->timeout = 30
  args->retr_time = 20
  args->flags = 1
  args->debug = 4
-- end args --
Reading in key file /etc/cluster/fence_xvm.key into 0xbf923b4c (4096 max size)
Actual key length = 4096 bytesOpened ckpt vm_states
My Node ID = 1
Domain                   UUID                                 Owner State
------                   ----                                 ----- -----
Domain-0                 00000000-0000-0000-0000-000000000000 00001 00001
node1                    8ab24c23-9592-4fd0-9626-c202f4006eb2 00001 00002
node2                    f05e5376-1f37-3630-fee4-2e5d8dfa18b6 00001 00002
node3                    e2d9464d-da96-f4f8-0126-888715d75768 00001 00002
Storing node1
Storing node2
Storing node3
Domain                   UUID                                 Owner State
------                   ----                                 ----- -----
Domain-0                 00000000-0000-0000-0000-000000000000 00001 00001
node1                    8ab24c23-9592-4fd0-9626-c202f4006eb2 00001 00002
node2                    f05e5376-1f37-3630-fee4-2e5d8dfa18b6 00001 00002
node3                    e2d9464d-da96-f4f8-0126-888715d75768 00001 00002
Storing node1
Storing node2
Storing node3
Domain                   UUID                                 Owner State
------                   ----                                 ----- -----
Domain-0                 00000000-0000-0000-0000-000000000000 00001 00001
node1                    8ab24c23-9592-4fd0-9626-c202f4006eb2 00001 00002
node2                    f05e5376-1f37-3630-fee4-2e5d8dfa18b6 00001 00002
node3                    e2d9464d-da96-f4f8-0126-888715d75768 00001 00002
Storing node1
Storing node2
Storing node3
Domain                   UUID                                 Owner State
------                   ----                                 ----- -----
Domain-0                 00000000-0000-0000-0000-000000000000 00001 00001
node1                    8ab24c23-9592-4fd0-9626-c202f4006eb2 00001 00002
node2                    f05e5376-1f37-3630-fee4-2e5d8dfa18b6 00001 00002
node3                    e2d9464d-da96-f4f8-0126-888715d75768 00001 00001
Storing node1
Storing node2
Storing node3
Hash mismatch:
PKT =
7bc9fb96397bb348d03f16d1b3498171734a122874477f5ab2eddd4cc40045a70000000000000000000000000000000000000000000000000000000000000000
EXP =
cd0c9da2bfdabb48018e08203f6932e7f224a57a01da1f000c62bd6179a628aa0000000000000000000000000000000000000000000000000000000000000000
Key mismatch; dropping packet
Domain                   UUID                                 Owner State
------                   ----                                 ----- -----
Domain-0                 00000000-0000-0000-0000-000000000000 00001 00001
node1                    8ab24c23-9592-4fd0-9626-c202f4006eb2 00001 00002
node2                    f05e5376-1f37-3630-fee4-2e5d8dfa18b6 00001 00002
node3                    e2d9464d-da96-f4f8-0126-888715d75768 00001 00002
Storing node1
Storing node2
Storing node3
Domain                   UUID                                 Owner State
------                   ----                                 ----- -----
Domain-0                 00000000-0000-0000-0000-000000000000 00001 00001
node1                    8ab24c23-9592-4fd0-9626-c202f4006eb2 00001 00002
node2                    f05e5376-1f37-3630-fee4-2e5d8dfa18b6 00001 00002
node3                    e2d9464d-da96-f4f8-0126-888715d75768 00001 00002
Storing node1
Storing node2
Storing node3
Hash mismatch:
PKT =
80bfd860db2599051562780d3b95fa664737c5d0a77d8a7a53a4bd20c2dfcd500000000000000000000000000000000000000000000000000000000000000000
EXP =
cd1e8b677119010e0dc9d20eeefbfeeffb8916a29c014f362e5afa30a8b663520000000000000000000000000000000000000000000000000000000000000000
Key mismatch; dropping packet
Domain                   UUID                                 Owner State
------                   ----                                 ----- -----
Domain-0                 00000000-0000-0000-0000-000000000000 00001 00001
node1                    8ab24c23-9592-4fd0-9626-c202f4006eb2 00001 00002
node2                    f05e5376-1f37-3630-fee4-2e5d8dfa18b6 00001 00002
node3                    e2d9464d-da96-f4f8-0126-888715d75768 00001 00002
Storing node1
Storing node2
Storing node3
Domain                   UUID                                 Owner State
------                   ----                                 ----- -----
Domain-0                 00000000-0000-0000-0000-000000000000 00001 00001
node1                    8ab24c23-9592-4fd0-9626-c202f4006eb2 00001 00002
node2                    f05e5376-1f37-3630-fee4-2e5d8dfa18b6 00001 00002
node3                    e2d9464d-da96-f4f8-0126-888715d75768 00001 00002
Storing node1
Storing node2
Storing node3


Comment 8 Thorsten Scherf 2008-04-09 13:24:39 EDT
wrong keys were used. 

closing

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