Bug 517355 - NFS mounting is not working for VM
Summary: NFS mounting is not working for VM
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: Virtualization Tools
Classification: Community
Component: ovirt-server-suite
Version: unspecified
Hardware: All
OS: Linux
low
medium
Target Milestone: ---
Assignee: Hugh Brock
QA Contact:
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2009-08-13 15:29 UTC by Sylvain Desbureaux
Modified: 2014-01-20 14:39 UTC (History)
3 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2014-01-20 14:39:19 UTC


Attachments (Terms of Use)

Description Sylvain Desbureaux 2009-08-13 15:29:48 UTC
Description of problem:
When a VM has an NFS mount "somewhere" (i.e. for storage or for mounting an iso image for a CD), the start of the VM fails even without selinux

Version-Release number of selected component (if applicable):
ovirt-build.noarch                    0.99-0.fc11
ovirt-node-image.x86_64               1.0.2-0.fc11.20090812121135git5d11d54
ovirt-node-image-pxe.x86_64           1.0.2-0.fc11.20090812121135git5d11d54
ovirt-release.noarch                  0.99-1.fc10
ovirt-server.noarch                   0.101-0.fc11.20090812115539git5db2ee4
ovirt-server-installer.noarch         0.101-0.fc11.20090812115539git5db2ee4

How reproducible:
always

Steps to Reproduce:
1.create a cobbler image with nfs (see the first command here slightly modified (don't put ':' between 'hostname.example.org' and '/path'): https://fedorahosted.org/cobbler/wiki/KoanWithIsos 
2. create a VM using the image for boot
3. start the VM
  
Actual results:
The VM doesn't start

Expected results:
The VM should start and have the iso image as CD


Additional info:
here's the log of taskomatic:

INFO Thu Aug 13 16:56:37 +0200 2009 (2094) starting task_start_vm
INFO Thu Aug 13 16:56:39 +0200 2009 (2094) VM will be started on node node84.open.net
DEBUG Thu Aug 13 16:56:39 +0200 2009 (2094) Connecting volumes: #<LvmStorageVolume:0x7fae0d85e8b0>#<NfsStorageVolume:0x7fae0d85cec0>
DEBUG Thu Aug 13 16:56:39 +0200 2009 (2094) Found existing storage pool nas.open.net-iqn.2006-01.com.openfiler:tsn.9a2bd39f003e-3260 on host: node84.open.net
DEBUG Thu Aug 13 16:56:39 +0200 2009 (2094) Verifying mount of pool :LvmStoragePool:#<LvmStoragePool:0x7fae0d8570d8>:
DEBUG Thu Aug 13 16:56:40 +0200 2009 (2094) Found existing storage pool ovirt_vg_1 on host: node84.open.net
DEBUG Thu Aug 13 16:56:40 +0200 2009 (2094) Pool mounted: ovirt_vg_1; state: running
DEBUG Thu Aug 13 16:56:40 +0200 2009 (2094) Verified volume of pool /dev/ovirt_vg_1/ubuntu-1
DEBUG Thu Aug 13 16:56:40 +0200 2009 (2094) Verifying mount of pool nas.open.net:NfsStoragePool:#<NfsStoragePool:0x7fae0d85bd68>:/mnt/nas/share/share
DEBUG Thu Aug 13 16:56:40 +0200 2009 (2094) Found existing storage pool nas.open.net-_mnt_nas_share_share on host: node84.open.net
DEBUG Thu Aug 13 16:56:41 +0200 2009 (2094) Pool mounted: nas.open.net-_mnt_nas_share_share; state: running
ERROR Thu Aug 13 16:56:41 +0200 2009 (2094) Task action processing failed: RuntimeError: Unable to find volume  attached to pool nas.open.net-_mnt_nas_share_share.
ERROR Thu Aug 13 16:56:41 +0200 2009 (2094) /usr/share/ovirt-server/task-omatic/taskomatic.rb:226:in `connect_storage_pools'/usr/share/ovirt-server/task-omatic/taskomatic.rb:193:in `each'/usr/share/ovirt-server/task-omatic/taskomatic.rb:193:in `connect_storage_pools'/usr/share/ovirt-server/task-omatic/taskomatic.rb:363:in `task_start_vm'/usr/share/ovirt-server/task-omatic/taskomatic.rb:904:in `mainloop'/usr/share/ovirt-server/task-omatic/taskomatic.rb:890:in `each'/usr/share/ovirt-server/task-omatic/taskomatic.rb:890:in `mainloop'/usr/share/ovirt-server/task-omatic/taskomatic.rb:856:in `loop'/usr/share/ovirt-server/task-omatic/taskomatic.rb:856:in `mainloop'/usr/share/ovirt-server/task-omatic/taskomatic.rb:957
INFO Thu Aug 13 16:56:41 +0200 2009 (2094) done





here's the log of the node :

Aug 13 14:56:39 node84 kernel: sd 6:0:0:0: [sdb] 204800000 512-byte hardware sectors: (104 GB/97.6 GiB)
Aug 13 14:56:39 node84 kernel: sd 6:0:0:0: [sdb] Write Protect is off
Aug 13 14:56:39 node84 kernel: sd 6:0:0:0: [sdb] Write cache: disabled, read cache: enabled, doesn't support DPO or FUA


SELinux is disabled everywhere

Comment 1 Cole Robinson 2014-01-20 14:39:19 UTC
This bugzilla product/component combination is no longer used: ovirt bugs are tracked under the bugzilla product 'oVirt'. If this bug is still valid, please reopen and set the correct product/component.


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