View Issue Details

IDProjectCategoryView StatusLast Update
0005737Talertwisterpublic2019-12-20 18:11
ReporterFlorian Dold Assigned ToMarcello Stanisci Resolution deadline
ImplementerReviewer 
Release signed byDeployed by 
VerifierCommunicator 
Data protection authority notification requiredNo  
CSIRT notification requiredNo  
Estimated effort (hours)Actual effort (hours)0 
Fast-trackNo
Work packagenone
PrioritynormalSeverityminorReproducibilityhave not tried
Status closedResolutionfixed 
Target Version0.6Fixed in Version0.6 
Summary0005737: twister should support chaos setting
DescriptionThis chaos setting (maybe specified in the config file) should allow to configure a chaos_probability between 0% and 100%.

For every request, with probability chaos_probability we do not send the actual response back, but instead a plain "service unavailable" response.
TagsNo tags attached.

Required notifications

Address or linkRemarkAdded byNotifiedActions

Activities

Marcello Stanisci

2019-05-30 12:28

reporter   ~0014461

You mean literally a "503 Service Unavailable" with empty/garbage response body?

Florian Dold

2019-05-30 19:51

manager   ~0014468

Yes!

Marcello Stanisci

2019-06-01 12:46

reporter   ~0014477

The chaos mode should NOT be used on 'demo' deployments; only 'test'.

Marcello Stanisci

2019-06-05 15:01

reporter   ~0014506

The chaos option was added here: bcb0c70..f66eb72. There is also a shell script "test_chaos.sh" under test/ that tells the user how many rounds it needed to hit a 5% "chaos" probability.

Marcello Stanisci

2019-06-06 15:49

reporter   ~0014513

0095cd3 adds the unix domain socket serving facility (prepping for 'test' deployment).

NOTE: removing the ".sock" file needs to be done!

Marcello Stanisci

2019-06-07 09:57

reporter   ~0014516

Actually, none of the other services remove the ".sock" file, so we'll keep things simple and not do for Twister neither.

Marcello Stanisci

2019-06-07 10:00

reporter   ~0014517

The chaos option is implemented (see notes above). Deployment on Gv is in progress.

Issue History

Date ModifiedUsernameFieldChange
2019-05-29 12:53Florian DoldNew Issue
2019-05-29 12:53Florian DoldStatusnew => assigned
2019-05-29 12:53Florian DoldAssigned To => Marcello Stanisci
2019-05-30 12:28Marcello StanisciNote Added: 0014461
2019-05-30 19:51Florian DoldNote Added: 0014468
2019-06-01 12:46Marcello StanisciNote Added: 0014477
2019-06-05 15:01Marcello StanisciNote Added: 0014506
2019-06-06 15:49Marcello StanisciNote Added: 0014513
2019-06-07 09:57Marcello StanisciNote Added: 0014516
2019-06-07 10:00Marcello StanisciStatusassigned => informing
2019-06-07 10:00Marcello StanisciResolutionopen => fixed
2019-06-07 10:00Marcello StanisciNote Added: 0014517
2019-12-20 18:11Christian GrothoffFixed in Version => 0.6
2019-12-20 18:11Christian GrothoffStatusinforming => closed