Bug 703351

Summary: Fail to create netfs pool having socket file
Product: Red Hat Enterprise Linux 5 Reporter: zhanghaiyan <yoyzhang>
Component: libvirtAssignee: Libvirt Maintainers <libvirt-maint>
Status: CLOSED WONTFIX QA Contact: Virtualization Bugs <virt-bugs>
Severity: medium Docs Contact:
Priority: medium    
Version: 5.7CC: dallan, dyuan, hjiang, llim, mshao, nzhang
Target Milestone: rc   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2011-08-15 19:45:37 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:

Description zhanghaiyan 2011-05-10 05:24:37 UTC
Description of problem:
If the nfs server has socket file in, then fail to create netfs pool on client.

Version-Release number of selected component (if applicable):
- libvirt-0.8.2-18.el5
- 2.6.18-259.el5
- kvm-83-231.el5

How reproducible:
always

Steps to Reproduce:
1. On nfs server 10.66.90.121:/vol/S3/libvirtmanual, happened to have socket files in.
# ll scim-socket-frontend-root
srw------- 1 root root 0 Mar 20 22:22 /mnt/scim-socket-frontend-root
# ll fcoemon.dcbd.1613 
srwxrwxrwx 1 root root 0 Jan 28 05:14 /mnt/fcoemon.dcbd.1613
2. On client, define a netfs pool 
# virsh pool-dumpxml pool-netfs
<pool type='netfs'>
  <name>pool-netfs</name>
  <uuid>c6c8d01b-ca67-a73a-baab-dbebf46c5cce</uuid>
  <capacity>0</capacity>
  <allocation>0</allocation>
  <available>0</available>
  <source>
    <host name='10.66.90.121'/>
    <dir path='/vol/S3/libvirtmanual'/>
    <format type='auto'/>
  </source>
  <target>
    <path>/var/lib/libvirt/images/pool-netfs</path>
    <permissions>
      <mode>0700</mode>
      <owner>-1</owner>
      <group>-1</group>
    </permissions>
  </target>
</pool>
3. Start the pool
# virsh pool-start pool-netfs
error: Failed to start pool pool-netfs
error: cannot open volume '/var/lib/libvirt/images/pool-netfs/scim-socket-frontend-root': No such device or address
4. Try to mount the nfs manually
# mount 10.66.90.121:/vol/S3/libvirtmanual /mnt
# ls /mnt
ca-cert.pem          rhel61_i386_10.img  rhel61_i386_graphic.img    vm15.img
orbit-root           rhel61_i386_19.img  scim-socket-frontend-root  vm5.img
.......
  
Actual results:
Failed to start the pool

Expected results:
Could succeed to start the pool as in step4 we could manually mount the nfs server having socket file. I guess pool-start should do actually the same thing.

Additional info:

Comment 1 Huming Jiang 2011-06-01 05:46:44 UTC
Could reproduce this bug on the following components of rh5.6:
kernel-2.6.18-238.el5
libvirt-0.8.2-15.el5
kvm-83-224.el5

Steps:
On Server:
1. #cat /etc/exports
/tmp *(rw,root_squash)
2. # ll /tmp
-r-------- 1 root root   18871 Jun  1 01:32 Bookmarks For New Hire-1.html
-r-------- 1 root root   18871 May 27 05:07 Bookmarks For New Hire.html
drwx------ 3 root root    4096 Jun  2 01:11 gconfd-root
srwxr-xr-x 1 root root       0 Jun  2 01:12 gedit.root.2220798103
drwx------ 2 root root    4096 Jun  2 01:11 keyring-l16O7U
srwxr-xr-x 1 root root       0 Jun  2 01:12 mapping-root
drwx------ 2 root root    4096 Jun  2 01:25 orbit-root
-r-------- 1 root root   68753 May 31 21:57 REDHAT_BJ^12438.pdf
srw------- 1 root root       0 Jun  2 01:12 scim-helper-manager-socket-root
srw------- 1 root root       0 Jun  2 01:12 scim-panel-socket:0-root
srw------- 1 root root       0 Jun  2 01:11 scim-socket-frontend-root

On client:
1. cat a.xml
<pool type='netfs'>
  <name>pool-netfs</name>
  <source>
    <host name='10.66.6.149'/>
    <dir path='/tmp'/>
    <format type='auto'/>
  </source>
  <target>
    <path>/var/lib/libvirt/images/pool-netfs</path>
  </target>
</pool>
2. #virsh pool-define a.xml 
Pool pool-netfs defined from a.xml
3. #virsh pool-start pool-netfs
error: Failed to start pool pool-netfs
error: cannot open volume '/var/lib/libvirt/images/pool-netfs/mapping-root': No such device or address
4. # mount 10.66.6.149:/tmp /mnt
5. # ll /mnt
total 2088
-r-------- 1 root root   18871 May 31 13:32 Bookmarks For New Hire-1.html
-r-------- 1 root root   18871 May 26 17:07 Bookmarks For New Hire.html
drwx------ 3 root root    4096 Jun  1 13:11 gconfd-root
srwxr-xr-x 1 root root       0 Jun  1 13:12 gedit.root.2220798103
drwx------ 2 root root    4096 Jun  1 13:11 keyring-l16O7U
srwxr-xr-x 1 root root       0 Jun  1 13:12 mapping-root
drwx------ 2 root root    4096 Jun  1 13:25 orbit-root
-r-------- 1 root root   68753 May 31 09:57 REDHAT_BJ^12438.pdf
srw------- 1 root root       0 Jun  1 13:12 scim-helper-manager-socket-root
srw------- 1 root root       0 Jun  1 13:12 scim-panel-socket:0-root
srw------- 1 root root       0 Jun  1 13:11 scim-socket-frontend-root

Comment 2 RHEL Program Management 2011-06-20 22:46:58 UTC
This request was evaluated by Red Hat Product Management for inclusion in Red Hat Enterprise Linux 5.7 and Red Hat does not plan to fix this issue the currently developed update.

Contact your manager or support representative in case you need to escalate this bug.

Comment 4 RHEL Program Management 2011-08-15 19:45:37 UTC
Development Management has reviewed and declined this request.  You may appeal
this decision by reopening this request.