Details
Improvement Request
Resolved
Major
-
- Environment:
- -
Issue Links
| Depends | |||
|---|---|---|---|
|
|||
Activity
| Field | Original Value | New Value |
|---|---|---|
| Assignee | Christophe DENEUX [ cdeneux ] | Victor NOËL [ vnoel ] |
| Priority | Major [ 3 ] | |
| Description |
Currently, during recovery, endpoints are re-activated and replace endpoints that were left (see PETALSESBCONT-XXX) in the previous execution of the container.
But if for some reasons some of the previously activated endpoints of the container are not re-activated during recovery, they should not be left as activated since it is 100% sure at that point that they won't be activated automatically anymore and that the only reasons that are activated again is by an administrative action. |
Currently, during recovery, endpoints are re-activated and replace endpoints that were left (see But if for some reasons some of the previously activated endpoints of the container are not re-activated during recovery, they should not be left as activated since it is 100% sure at that point that they won't be activated automatically anymore and that the only reasons that are activated again is by an administrative action. |
| Status | New [ 10000 ] | Open [ 10002 ] |
| Link |
This issue depends on |
| Status | Open [ 10002 ] | In Progress [ 10003 ] |
| Status | In Progress [ 10003 ] | Resolved [ 10004 ] |
| Fix Version/s | 5.0.2 [ 10661 ] | |
| Resolution | Fixed [ 1 ] |