Bug 952973

+++ This bug was initially created as a clone of Bug #952972 +++

Description of problem:
create a invalid logical pool via pool-create-as with wrong --target device
vg should be new which has not lv in it .

Version-Release number of selected component (if applicable):
libvirt-0.10.2-18.el6_4.4.x86_64
libvirt-1.0.4-1.el7.x86_64

How reproducible:
100

Steps to Reproduce:
1. create a logical pool or define then start
create a invalid logical pool via pool-create-as with wrong --target
device which vg has not lv in it.
# virsh pool-create-as sd3 --type logical --target /dev
Pool sd3 created

2.try to create vol via vol-create
# virsh vol-create-as sd3 v1 100M
error: Failed to create vol v1
error: cannot stat file '/dev/v1': No such file or directory

3.create vol via lvm cmd
# lvcreate sd3 --name v1 -L 100M
Logical volume "v1" created
[root@6-217 tmp]# lvs
LV VG Attr LSize Pool Origin Data% Move Log Cpy%Sync Convert
v1 sd3 -wi-a---- 100.00m
[root@6-217 tmp]# ll /dev/sd3/v1
lrwxrwxrwx. 1 root root 7 Apr 16 03:14 /dev/sd3/v1 -> ../dm-0

4.the vol created by lvm cmd will disappear after run vol-create-as
# virsh vol-create-as sd3 v1 100M
error: Failed to create vol v1
error: internal error Child process (/sbin/lvcreate --name v1 -L 102400K
sd3) unexpected exit status 5: Logical volume "v1" already exists in
volume group "sd3"

# lvs
# ll /dev/sd3/v1
ls: cannot access /dev/sd3/v1: No such file or directory

Actual results:
as steps

Expected results:
check target if wrong report error
step4 should not affect vol already created .

Additional info: