| Summary: | [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' | ||||||||
|---|---|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | dimapunk80 | ||||||
| Component: | vdsm | Assignee: | Federico Simoncelli <fsimonce> | ||||||
| Status: | CLOSED CURRENTRELEASE | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||||
| Severity: | unspecified | Docs Contact: | |||||||
| Priority: | unspecified | ||||||||
| Version: | 19 | CC: | amureini, danken, dougsland, fsimonce, virt-maint, ybronhei | ||||||
| Target Milestone: | --- | ||||||||
| Target Release: | --- | ||||||||
| Hardware: | x86_64 | ||||||||
| OS: | Unspecified | ||||||||
| URL: | https://retrace.fedoraproject.org/faf/reports/bthash/209ad1bd01337a0e27ee52c16b81d9f13b0084b0 | ||||||||
| Whiteboard: | abrt_hash:a6bd6b0f2669a69286a6b28c8d95290fbf21bbbe | ||||||||
| Fixed In Version: | Doc Type: | Bug Fix | |||||||
| Doc Text: | Story Points: | --- | |||||||
| Clone Of: | Environment: | ||||||||
| Last Closed: | 2015-01-11 12:58: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: | |||||||
| Attachments: |
|
||||||||
Created attachment 826847 [details]
File: backtrace
Created attachment 826848 [details]
File: environ
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. |
Version-Release number of selected component: vdsm-python-4.12.1-4.fc19 Additional info: reporter: libreport-2.1.9 cmdline: /usr/bin/python /usr/bin/vdsm-tool sanlock-check-service executable: /usr/bin/vdsm-tool kernel: 3.11.7-200.fc19.x86_64 runlevel: N 5 type: Python uid: 0 Truncated backtrace: 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> sys.exit(main()) File "/usr/bin/vdsm-tool", line 140, in main return tool_command[cmd]["command"](*args[1:]) 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: args: ()