** Description changed:

+ 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
+  * 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="/etc/init.d/clvm" name="clvm"/>
-   </resources>
+   <resources>
+    <script file="/etc/init.d/clvm" name="clvm"/>
+   </resources>
  
-   <service autostart="1" domain="only1" exclusive="0" name="clvm1" 
recovery="restart">
-    <script ref="clvm"/>
-   </service>
- 
- Is it possible to change this behavior like that:
- # /etc/init.d/clvm status ; echo $?
-  * Cluster LVM Daemon is not running
- 1
- 
- E.g. like proposed in my patch?
- 
- Best regards
- Christian
+   <service autostart="1" domain="only1" exclusive="0" name="clvm1" 
recovery="restart">
+    <script ref="clvm"/>
+   </service>

-- 
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/988881

Title:
  /etc/init.d/clvm status exitcode always 0

To manage notifications about this bug go to:
https://bugs.launchpad.net/ubuntu/+source/lvm2/+bug/988881/+subscriptions

-- 
ubuntu-bugs mailing list
ubuntu-bugs@lists.ubuntu.com
https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs

Reply via email to