Bug 1091588

Description of problem:

I create fence_virt.conf using 'fence_virtd -c' and told it to use 'key_file = "/etc/fence_xvm.key";'. However, when trying to start it, it failed with:

====
# fence_xvm -o list
Could not read /etc/cluster/fence_xvm.key; trying without authentication
====

When I created a symlink, it worked:

====
# mkdir /etc/cluster
# ln -s /etc/fence_xvm.key /etc/cluster/fence_xvm.key
# fence_xvm -o list
an-c06n01            c85b93e9-9440-4643-8cc1-b243c32a3278 on
an-c06n02            878de2ac-3eb2-4304-b682-a249420c0205 on
====

Version-Release number of selected component (if applicable):

# rpm -q fence-virt
fence-virt-0.3.0-15.fc20.x86_64

How reproducible:

tried once, probably 100%

Steps to Reproduce:
1. Setup that caused triggered the bug below.
2.
3.

====
  0 root@lemass:/home/digimer# fence_virtd -c
Module search path [/usr/lib64/fence-virt]: 

Available backends:
    libvirt 0.1
Available listeners:
    multicast 1.2

Listener modules are responsible for accepting requests
from fencing clients.

Listener module [multicast]: 

The multicast listener module is designed for use environments
where the guests and hosts may communicate over a network using
multicast.

The multicast address is the address that a client will use to
send fencing requests to fence_virtd.

Multicast IP Address [225.0.0.12]: 

Using ipv4 as family.

Multicast IP Port [1229]: 

Setting a preferred interface causes fence_virtd to listen only
on that interface.  Normally, it listens on all interfaces.
In environments where the virtual machines are using the host
machine as a gateway, this *must* be set (typically to virbr0).
Set to 'none' for no interface.

Interface [virbr0]: virbr2

The key file is the shared key information which is used to
authenticate fencing requests.  The contents of this file must
be distributed to each physical host and virtual machine within
a cluster.

Key File [/etc/cluster/fence_xvm.key]: /etc/fence_xvm.key

Backend modules are responsible for routing requests to
the appropriate hypervisor or management layer.

Backend module [libvirt]: 

Configuration complete.

=== Begin Configuration ===
backends {
	libvirt {
		uri = "qemu:///system";
	}

}

listeners {
	multicast {
		port = "1229";
		family = "ipv4";
		interface = "virbr2";
		address = "225.0.0.12";
		key_file = "/etc/fence_xvm.key";
	}

}

fence_virtd {
	module_path = "/usr/lib64/fence-virt";
	backend = "libvirt";
	listener = "multicast";
}

=== End Configuration ===
Replace /etc/fence_virt.conf with the above [y/N]? y
  0 root@lemass:/home/digimer# fence_virtd
  0 root@lemass:/home/digimer# pidof fence_virtd
15255
  0 root@lemass:/home/digimer# fence_xvm -o list
Could not read /etc/cluster/fence_xvm.key; trying without authentication
====

Actual results:

key file not used.

Expected results:

key file used.


Additional info: