Bug 847515 - Not all required kernel modules are loaded for the sanlock to run (create NFS Storage Pool will fail)
Not all required kernel modules are loaded for the sanlock to run (create NFS...
Product: Red Hat Enterprise Linux 6
Classification: Red Hat
Component: ovirt-node (Show other bugs)
Unspecified Unspecified
urgent Severity urgent
: rc
: ---
Assigned To: Mike Burns
Virtualization Bugs
: TestBlocker, ZStream
Depends On:
Blocks: 847773
  Show dependency treegraph
Reported: 2012-08-12 09:30 EDT by Ilanit Stein
Modified: 2016-04-26 10:05 EDT (History)
22 users (show)

See Also:
Fixed In Version: ovirt-node-2.5.0-3.el6
Doc Type: Bug Fix
Doc Text:
Previously, sanlock service would not run because not all required kernel modules were loaded. Creating a storage pool failed as a result. This has been corrected so now creating storage pools does not fail.
Story Points: ---
Clone Of:
Last Closed: 2013-02-28 11:38:06 EST
Type: Bug
Regression: ---
Mount Type: ---
Documentation: ---
Verified Versions:
Category: ---
oVirt Team: ---
RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: ---

Attachments (Terms of Use)
engine log (473.96 KB, application/x-compressed-tar)
2012-08-12 09:36 EDT, Ilanit Stein
no flags Details
/var/log/messages (46.51 KB, application/x-compressed-tar)
2012-08-12 09:58 EDT, Ilanit Stein
no flags Details

  None (edit)
Description Ilanit Stein 2012-08-12 09:30:56 EDT
Description of problem:

On rhev-hypervisor6-6.3-20120808.0.rhev31.el6_3, (vdsm-4.9.6-27.0.el6_3.x86_64) sanlock service is not running because not all required kernel modules are loaded. Create storage pool fails as a result.

On host:

[root@white-vdse ~]# /etc/init.d/wdmd start
Loading the softdog kernel module: FATAL: Could not open '/lib/modules/2.6.32-279.5.1.el6.x86_64/kernel/drivers/watchdog/softdog.ko': No such file or directory
Starting wdmd:                                             [  OK  ]

Error from vdsm.log:

Thread-276::INFO::2012-08-12 11:05:02,613::safelease::160::SANLock::(acquireHostId) Acquiring host id for domain 95e87338-e784-42e1-a0ec-25901ba7c336 (id: 250)
Thread-276::ERROR::2012-08-12 11:05:02,614::task::853::TaskManager.Task::(_setError) Task=`c2be8ab3-b760-4654-a291-c1f8b179741c`::Unexpected error
Traceback (most recent call last):
  File "/usr/share/vdsm/storage/task.py", line 861, in _run
  File "/usr/share/vdsm/logUtils.py", line 38, in wrapper
  File "/usr/share/vdsm/storage/hsm.py", line 788, in createStoragePool
  File "/usr/share/vdsm/storage/sp.py", line 569, in create
  File "/usr/share/vdsm/storage/sp.py", line 510, in _acquireTemporaryClusterLock
  File "/usr/share/vdsm/storage/sd.py", line 415, in acquireHostId
  File "/usr/share/vdsm/storage/safelease.py", line 175, in acquireHostId
AcquireHostIdFailure: Cannot acquire host id: ('95e87338-e784-42e1-a0ec-25901ba7c336', SanlockException(2, 'Sanlock lockspace add failure', 'No such file or directory'))

How reproducible:
Comment 1 Ilanit Stein 2012-08-12 09:32:31 EDT
bug marked as test blocker as it fails many testcases in rhev-h rest api test.
Comment 2 Ilanit Stein 2012-08-12 09:36:02 EDT
Created attachment 603775 [details]
engine log
Comment 4 Ilanit Stein 2012-08-12 09:58:19 EDT
Created attachment 603777 [details]
Comment 6 Ilanit Stein 2012-08-12 16:09:42 EDT
more info:
whole 'watchdog' driver directory is missing:

[root@white-vdse ~]# ls  /lib/modules/2.6.32-279.5.1.el6.x86_64/kernel/drivers/
ata    cdrom  cpufreq  dma   firmware  infiniband  message  pci   uio  vhost
block  char   dca      edac  idle      md          net      scsi  usb  virtio
Comment 7 Mike Burns 2012-08-12 20:51:42 EDT
Upstream is already fixed to include the watchdog directory


Patch is already included in 6.4 stream.
Comment 8 cshao 2012-08-13 02:40:08 EDT
Test version:
rhevm-si13.2 (rhevm-3.1.0-11.el6ev.noarch)

Test result:
1. If set compatibility version to 3.0 when create data centers, connect NFS/iscsi/FC storage can successful.
2. If set compatibility version to 3.1, can reproduce the same issue.
Comment 16 errata-xmlrpc 2013-02-28 11:38:06 EST
Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.


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