/etc/init.d/clvm status exitcode always 0
Affects | Status | Importance | Assigned to | Milestone | |
---|---|---|---|---|---|
lvm2 (Ubuntu) |
Fix Released
|
Undecided
|
Andres Rodriguez | ||
Precise |
Fix Released
|
Medium
|
Dimitri John Ledkov | ||
Quantal |
Fix Released
|
Undecided
|
Andres Rodriguez |
Bug Description
Impact:
* Cannot use clvm as a cluster resource.
Test case:
# /etc/init.d/clvm stop; /etc/init.d/clvm status; echo $?
* Cluster LVM Daemon is not running
3
# /etc/init.d/clvm start; /etc/init.d/clvm status; echo $?
* Cluster LVM Daemon is running
0
Regression potential:
If there were tests out there that did pattern matching on the text and check for exit code 0, they will now fail to detect that clvm is not running (since exit code has changed to 3 now).
Description:
# /etc/init.d/clvm status ; echo $?
* Cluster LVM Daemon is not running
0
/etc/init.d/clvm is showing, that Cluster LVM Daemon is not running, but it always exits with 0.
So processes that controll CLVM using "/etc/init.d/clvm status", that rely on correct exit codes, are going to fail.
In consequence it is not possible to use "/etc/init.d/clvm" as a script to a resource in "cluster.conf".
You cannot do sth. like:
<resources>
<script file="/
</resources>
<service autostart="1" domain="only1" exclusive="0" name="clvm1" recovery="restart">
<script ref="clvm"/>
</service>
Changed in lvm2 (Ubuntu Quantal): | |
assignee: | nobody → Andres Rodriguez (andreserl) |
Changed in lvm2 (Ubuntu Precise): | |
status: | New → In Progress |
importance: | Undecided → Medium |
assignee: | nobody → Dmitrijs Ledkovs (xnox) |
description: | updated |
Affected:
# lsb_release -rd
Description: Ubuntu 12.04 LTS
Release: 12.04
# dpkg -l clvm libdevmapper1.02.1 lvm2 4ubuntu7. 1~ppa1 Cluster LVM Daemon for lvm2
ii clvm 2.02.66-