Bug #354

one start fails silently

Added by Marc-Elian Begin about 9 years ago. Updated over 8 years ago.

Status:ClosedStart date:09/22/2010
Priority:NormalDue date:
Assignee:-% Done:

0%

Category:-
Target version:-
Resolution:fixed Pull request:
Affected Versions:

Description

When errors occur in the execution of 'one start', the command still reports success. This is misleading as the only way to verify that the daemon launched properly is to go through the logs.

Issue linked to StratusLab: http://jira.stratuslab.eu:8080/browse/STRATUSLAB-175

Associated revisions

Revision 96c4cbc2
Added by Javi Fontan almost 9 years ago

bug #354: typo in one start script

Revision a821bf84
Added by Ruben S. Montero almost 9 years ago

bug #354: Fix if statement and reduced time to check for the daemons

Revision f1bff01c
Added by Ruben S. Montero almost 9 years ago

bug #354: kills any running daemon if OpenNebula fails to start

Revision 0ad0cda4
Added by Javi Fontan almost 9 years ago

Merged changes from bug-354 (#354)

f1bff01 bug #354: kills any running daemon if OpenNebula fails to start
a821bf8 bug #354: Fix if statement and reduced time to check for the daemons
96c4cbc bug #354: typo in one start script
eec200f bug-354: check that the daemons have started
c883bab Fixing whitespace for one script

Revision d3283b29
Added by Javi Fontan over 2 years ago

Merge pull request #354 from Semedi/master

B #5056 EC2 elastic ip functionality broken

History

#1 Updated by Javi Fontan about 9 years ago

  • Target version deleted (Release 2.0)

#2 Updated by Ruben S. Montero over 8 years ago

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

Also available in: Atom PDF