Red Hat Bugzilla – Bug 1032792
[abrt] vdsm-python-4.12.1-4.fc19: sanlock.py:41:sanlock_check_service:IOError: [Errno 2] No such file or directory: '/var/run/sanlock/sanlock.pid'
Last modified: 2015-01-11 07:58:37 EST
Version-Release number of selected component:
cmdline: /usr/bin/python /usr/bin/vdsm-tool sanlock-check-service
runlevel: N 5
sanlock.py:41:sanlock_check_service:IOError: [Errno 2] No such file or directory: '/var/run/sanlock/sanlock.pid'
Traceback (most recent call last):
File "/usr/bin/vdsm-tool", line 143, in <module>
File "/usr/bin/vdsm-tool", line 140, in main
File "/usr/lib64/python2.7/site-packages/vdsm/tool/sanlock.py", line 41, in sanlock_check_service
sanlock_pid = open(SANLOCK_PID, "r").readline().strip()
IOError: [Errno 2] No such file or directory: '/var/run/sanlock/sanlock.pid'
Local variables in innermost frame:
Created attachment 826847 [details]
Created attachment 826848 [details]
Yaniv you did some work on this recently. Is this fixed already?
yes, since 4.13.x if sanlock is not running this function will report True and print to stdout that sanlock is down. i would close it on CURRENTRELEASE unless you want to fix it on 4.12.x
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.
(In reply to Yaniv Bronhaim from comment #4)
> yes, since 4.13.x if sanlock is not running this function will report True
> and print to stdout that sanlock is down. i would close it on CURRENTRELEASE
> unless you want to fix it on 4.12.x
Closing as CURRENTRELEASE, based on this comment.