Scénario #15483
Agent RVP : revoir le traitement des threads strongSwan et ajouter un status.error dans un cas précis
Status:
Terminé (Sprint)
Priority:
Normal
Assigned To:
Category:
-
Target version:
Start date:
10/12/2015
Due date:
09/23/2016
% Done:
100%
Estimated time:
(Total: 6.00 h)
Spent time:
(Total: 8.28 h)
Story points:
3.0
Remaining (hours):
0.00 hour
Velocity based estimate:
Release:
Release relationship:
Auto
Description
- le nombre de threads strongSwan renvoyés par parse_ipsec_statusall n'est pas toujours exact
- Relance du service rvp en cas d'état des process ipsec incohérent
- cohérence entre diagnose et agent
Subtasks
History
#1 Updated by Scrum Master over 7 years ago
- Tracker changed from Proposition Scénario to Scénario
- Start date deleted (
10/12/2015) - Release set to EOLE 2.6.0
- Story points set to 3.0
#2 Updated by Luc Bourdot about 7 years ago
- Due date set to 09/23/2016
- Target version set to sprint 2016 36-38 - Équipe MENSR
- Start date set to 09/05/2016
#3 Updated by Joël Cuissinat about 7 years ago
- Assigned To set to force orange
#4 Updated by Fabrice Barconnière about 7 years ago
- Status changed from Nouveau to Terminé (Sprint)