Comment 3 for bug 1966176

Revision history for this message
Maurice Escher (maurice-escher) wrote :

I did not try to reproduce it.
Only additional info I can share is, that (additional to the real customer workload) we have periodic tests running that create a share, add access-rules, mount the share and delete the share. I can imagine that the restart is happening after the access rule api call has been made.
And then the test is sending a delete share api call, because the rule does not get active within our configured test-timeout (1 minute in our case).

We run this every 5 minutes in every availability zone, so there is not too much going on in parallel, only the timing of the restart is bad luck sometimes.

I saw this error roughly estimated only once in 200 manila-share restarts.