Petals CDK

The CDK should revert SU state in case of failure of SU deploy, init and start

View this issue in another formatViewView
- XML
- Word
- Printable

Details

Type: Improvement Request
Status: Resolved
Priority: Major
Resolution: Fixed
Affects Version/s: 5.5.0
Fix Version/s: 5.6.0
Component/s: None
Security Level: Public

Description:

Hide

According to the JBI specification, it is the responsibility of the component to take care its own state in case of failure of deploy, init and start of service units on top of throwing an exception (see also ~~PETALSCDK-166~~).

It means that if the execution of component specific doDeploy, doInit and doStart fails, they the opposite doUndeploy, doShutdown and doStop are called.

Show
According to the JBI specification, it is the responsibility of the component to take care its own state in case of failure of deploy, init and start of service units on top of throwing an exception (see also ~~PETALSCDK-166~~). It means that if the execution of component specific doDeploy, doInit and doStart fails, they the opposite doUndeploy, doShutdown and doStop are called.

Environment:

-

Issue Links

Depends

This issue blocks:
~~PETALSCDK-166~~ SU lifecycle operations should throw exceptions in case of failure
~~PETALSESBCONT-404~~ The Container shouldn't try to revert deployment in case of failure
~~PETALSDISTRIB-240~~ Rework Component/SA/SU lifecycle against error situations
~~PETALSESBCONT-405~~ Remove the UNKNOWN state for SAs and SUs

Activity

Transition

Status Change Time

Execution Times

Last Executer

Last Execution Date

New

Open

8s

1

Victor NOËL

Mon, 7 Mar 2016 - 15:44:07 +0100

Open

In Progress

15s

1

Victor NOËL

Mon, 7 Mar 2016 - 15:44:22 +0100

In Progress

Resolved

28m 5s

1

Victor NOËL

Mon, 7 Mar 2016 - 16:12:27 +0100

People

Assignee:

Victor NOËL

Reporter:

Victor NOËL
Watchers:

0

Dates

Created:

Mon, 7 Mar 2016 - 15:43:59 +0100

Updated:

Tue, 22 Mar 2016 - 17:06:42 +0100

Resolved:

Mon, 7 Mar 2016 - 16:12:27 +0100