Bug 968212
| Summary: | Fdora19:Alpha: dmeventd Child exited with code 1 | ||||||
|---|---|---|---|---|---|---|---|
| Product: | [Fedora] Fedora | Reporter: | IBM Bug Proxy <bugproxy> | ||||
| Component: | lvm2 | Assignee: | Peter Rajnoha <prajnoha> | ||||
| Status: | CLOSED ERRATA | QA Contact: | Fedora Extras Quality Assurance <extras-qa> | ||||
| Severity: | medium | Docs Contact: | |||||
| Priority: | unspecified | ||||||
| Version: | 19 | CC: | agk, bmarzins, bmr, dwysocha, heinzm, jkachuck, jonathan, lvm-team, msnitzer, prajnoha, prockai, wgomerin, zkabelac | ||||
| Target Milestone: | --- | ||||||
| Target Release: | --- | ||||||
| Hardware: | ppc64 | ||||||
| OS: | All | ||||||
| Whiteboard: | |||||||
| Fixed In Version: | lvm2-2.02.98-12.fc19 | Doc Type: | Bug Fix | ||||
| Doc Text: | Story Points: | --- | |||||
| Clone Of: | Environment: | ||||||
| Last Closed: | 2013-08-23 00:34:19 UTC | Type: | --- | ||||
| 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
IBM Bug Proxy
2013-05-29 08:40:35 UTC
Created attachment 754262 [details]
dmeventd -V exist status correction. (wrong diff , reattaching the patch) Ignore previous patch ( attachment 79957 )
(In reply to IBM Bug Proxy from comment #0) > I think - the 'dmeventd -d' o/p run the second time must exit with exit > status 1. Please correct me here. Yes, that must return 1 to indicate failure here as only one instance should be running at a time. > Now, I agree with you that dmeventd -V must *always* return exist status 0 > - and it does so (see above results) irrespective of the fact that the > dmeventd daemon is running/not running. Please find the patch attached for > these results. > > Please let me know if these results are acceptable. > Yes, that should be return 0. Thanks for spotting this! Committed upstream. https://git.fedorahosted.org/cgit/lvm2.git/commit/?id=6ad17fd7129dc7f50c0623181681157faea806a1 lvm2-2.02.98-12.fc19 has been submitted as an update for Fedora 19. https://admin.fedoraproject.org/updates/lvm2-2.02.98-12.fc19 Package lvm2-2.02.98-12.fc19: * should fix your issue, * was pushed to the Fedora 19 testing repository, * should be available at your local mirror within two days. Update it with: # su -c 'yum update --enablerepo=updates-testing lvm2-2.02.98-12.fc19' as soon as you are able to. Please go to the following url: https://admin.fedoraproject.org/updates/FEDORA-2013-15098/lvm2-2.02.98-12.fc19 then log in and leave karma (feedback). lvm2-2.02.98-12.fc19 has been pushed to the Fedora 19 stable repository. If problems still persist, please make note of it in this bug report. ------- Comment From rragipal.com 2013-10-18 09:19 EDT------- This behaviour is working fine in Fedora20 Alpha. [root@juno-ioxc1-lp3 ras]# uname -a Linux juno-ioxc1-lp3.austin.ibm.com 3.11.4-301.fc20.ppc64p7 #1 SMP Thu Oct 10 11:24:10 MST 2013 ppc64 ppc64 ppc64 GNU/Linux [root@juno-ioxc1-lp3 ras]# dmeventd -V ; echo $? dmeventd version: 1.02.81 (2013-09-23) [root@juno-ioxc1-lp3 ras]# dmeventd -d ; echo $? [root@juno-ioxc1-lp3 ras]# ps -ef | grep dmev root 25147 1 0 04:15 ? 00:00:00 dmeventd -d root 25149 23938 0 04:15 pts/1 00:00:00 grep --color=auto dmev [root@juno-ioxc1-lp3 ras]# rpm -qa | grep lvm2 lvm2-libs-2.02.102-1.fc20.ppc64 lvm2-2.02.102-1.fc20.ppc64 [root@juno-ioxc1-lp3 ras]# ------- Comment From shubgoya.com 2013-10-18 14:32 EDT------- Closed per comment 21... |