Bug #3374

exit code is always 0 if you call up the init script with "status"

Added by Thilo Wening over 5 years ago. Updated about 4 years ago.

Status:ClosedStart date:11/21/2014
Priority:NormalDue date:
Assignee:Javi Fontan% Done:

0%

Category:Packaging
Target version:Release 5.0
Resolution:wontfix Pull request:
Affected Versions:Development

Description

We are running puppet and we are checking the status of the sunstone server.
If the status code is 0 he is running and will be stopped.

But every init script which is executed with the argument status, the exit code will be 0.
For us that means, for example the sunstone server is always running, even if it is stopped.

This false exit code is caused of an colon at the last line of the init files.
And colon is an alias for 0.
-------------------------------------------------------------
egrep :$ /etc/init.d/opennebula*
/etc/init.d/opennebula::
/etc/init.d/opennebula-econe::
/etc/init.d/opennebula-flow::
/etc/init.d/opennebula-novnc::
/etc/init.d/opennebula-sunstone::
-------------------------------------------------------------


Related issues

Related to Feature #4029: Systemd scripts for Debian/Ubuntu packages Closed 10/06/2015

Associated revisions

Revision 99050640
Added by Javi Fontan over 4 years ago

bug #3374: fix status result for Debian and Ubuntu

Revision 7724a1c8
Added by Javi Fontan over 4 years ago

bug #3374: fix status result for Debian and Ubuntu

(cherry picked from commit 99050640920072099bd9448bca4954ffa5ba543a)

Revision ea0074e8
Added by Javi Fontan over 4 years ago

Revert "bug #3374: fix status result for Debian and Ubuntu"

This reverts commit 99050640920072099bd9448bca4954ffa5ba543a.

Breaks service startup

Revision ba28277d
Added by Javi Fontan over 4 years ago

Revert "bug #3374: fix status result for Debian and Ubuntu"

This reverts commit 7724a1c88346d24e3f7796c310e1effb053839ed.

Breaks service startup

History

#1 Updated by Ruben S. Montero over 5 years ago

  • Category changed from Core & System to Packaging

#2 Updated by Ruben S. Montero almost 5 years ago

  • Related to Feature #4029: Systemd scripts for Debian/Ubuntu packages added

#3 Updated by Ruben S. Montero almost 5 years ago

  • Target version set to Release 5.0

#4 Updated by Javi Fontan almost 5 years ago

  • Assignee set to Javi Fontan
  • Target version changed from Release 5.0 to Release 4.14.2

#5 Updated by Javi Fontan over 4 years ago

  • Status changed from Pending to Closed
  • Resolution set to fixed

#6 Updated by Javi Fontan over 4 years ago

  • Status changed from Closed to Pending
  • Resolution deleted (fixed)

This change breaks service startup. Reverting changes.

We will revisit this problem later. Maybe changing the startup scripts to native systemd.

#7 Updated by Javi Fontan over 4 years ago

  • Target version changed from Release 4.14.2 to Release 5.0

#8 Updated by Javi Fontan about 4 years ago

  • Status changed from Pending to Closed
  • Resolution set to wontfix

New releases of Debian and Ubuntu packages (8 and 16.04) use systemd startup. We are not going to change the init scripts for Ubuntu 14.04.

Also available in: Atom PDF