Bug 1045512

Summary: Watchdog device unusable by sanlock - Lenovo S30
Product: [Fedora] Fedora Reporter: Pascal Jakobi <pascal.jakobi>
Component: sanlockAssignee: David Teigland <teigland>
Status: CLOSED CURRENTRELEASE QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 19CC: amureini, cfeist, fsimonce, teigland
Target Milestone: ---   
Target Release: ---   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2015-01-12 15:16:40 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Attachments:
Description Flags
lsmod output
none
lspci output none

Description Pascal Jakobi 2013-12-20 15:43:20 UTC
Created attachment 839630 [details]
lsmod output

Description of problem:  Watchdog device (probably provided by the
motherboard of your pc/server) not currently usable by wdmd


Version-Release number of selected component (if applicable): sanlock-2.8-1.fc19.x86_64


How reproducible: Add an NFS storage domain with ovirt 3.3


Steps to Reproduce:
1.
2.
3.

Actual results: Failure. See logs
> Dec 18 16:46:05 lab2 systemd-wdmd[818]: Starting wdmd: [  OK  ]
> Dec 18 16:46:05 lab2 systemd[1]: Unit wdmd.service entered failed state.
> Dec 18 20:52:12 lab2 wdmd[887]: wdmd started S0 H1 G179
> Dec 18 20:52:12 lab2 wdmd[887]: /dev/watchdog0 failed to set timeout
> Dec 18 20:52:12 lab2 wdmd[887]: /dev/watchdog0 disarmed
> Dec 18 20:52:12 lab2 wdmd[887]: /dev/watchdog failed to set timeout
> Dec 18 20:52:12 lab2 wdmd[887]: /dev/watchdog disarmed
> Dec 18 20:52:12 lab2 wdmd[887]: no watchdog device, load a watchdog driver
> Dec 18 20:52:12 lab2 systemd[1]: wdmd.service: main process exited,
> code=exited, status=255/n/a



Expected results: OK


Additional info:

Comment 1 Pascal Jakobi 2013-12-20 15:44:08 UTC
Created attachment 839631 [details]
lspci output

Comment 2 Federico Simoncelli 2013-12-20 15:56:21 UTC
David, do you think we can make wdmd automatically load the softdog in these cases?

If you don't want to load the module directly from wdmd maybe you can provide a command line to run in order to check if there's any watchdog available.

Currently the wdmd init script runs:

watchdog_check() {
        if [ ! -c /dev/watchdog ]; then
                echo -n $"Loading the softdog kernel module: "
                modprobe softdog && udevadm settle
                [ -c /dev/watchdog ] && success || failure
                echo
        fi
}

we could use something like:

 wdmd --probe-watchdogs

instead of the simple "! -c /dev/watchdog" check.

What do you think?

Comment 3 David Teigland 2013-12-23 17:01:31 UTC
Yes, I will add an option for that.

Comment 4 Fedora End Of Life 2015-01-09 20:55:21 UTC
This message is a notice that Fedora 19 is now at end of life. Fedora 
has stopped maintaining and issuing updates for Fedora 19. It is 
Fedora's policy to close all bug reports from releases that are no 
longer maintained. Approximately 4 (four) weeks from now this bug will
be closed as EOL if it remains open with a Fedora 'version' of '19'.

Package Maintainer: If you wish for this bug to remain open because you
plan to fix it in a currently maintained version, simply change the 'version' 
to a later Fedora version.

Thank you for reporting this issue and we are sorry that we were not 
able to fix it before Fedora 19 is end of life. If you would still like 
to see this bug fixed and are able to reproduce it against a later version 
of Fedora, you are encouraged  change the 'version' to a later Fedora 
version prior this bug is closed as described in the policy above.

Although we aim to fix as many bugs as possible during every release's 
lifetime, sometimes those efforts are overtaken by events. Often a 
more recent Fedora release includes newer upstream software that fixes 
bugs or makes them obsolete.

Comment 5 Allon Mureinik 2015-01-11 12:39:24 UTC
(In reply to David Teigland from comment #3)
> Yes, I will add an option for that.

According to comment 4, this bug is about to be closed as EOL. Should we bump it forward to F20/F21?

Comment 6 David Teigland 2015-01-12 15:16:40 UTC
This was fixed.