[tahoe-lafs-trac-stream] [tahoe-lafs] #2025: test storage server behaviour for bad container files or chunk objects (was: test storage server behaviour for bad container files)

[tahoe-lafs]

#2025: test storage server behaviour for bad container files or chunk objects
-------------------------+-------------------------------------------------
     Reporter:  daira    |      Owner:
         Type:  defect   |     Status:  new
     Priority:  normal   |  Milestone:  soon
    Component:  code-    |    Version:  1.10.0
  storage                |   Keywords:  test error corruption cloud-backend
   Resolution:           |
Launchpad Bug:           |
-------------------------+-------------------------------------------------
Description changed by daira:

Old description:

> The behaviour of a storage server on shares with a corrupt container (bad
> header or inconsistent length) is insufficiently tested. We should
> simulate various kinds of container corruption (also on a subset of
> shares in a shareset that has more than one share), to test that the
> correct errors are raised.
>
> See for example [https://github.com/LeastAuthority/tahoe-
> lafs/commit/fd819cea11599cc274b8e1d72bfce0fffea39296#L3R93 this bug],
> which showed that raising {{{CorruptStoredShareError}}} on an immutable
> share with an inconsistent length was untested.
>
> Note that the code and the intended behaviour (see #1566) has changed on
> the cloud branch so that is what we should test. The cloud backend has
> additional failure modes due to missing or inconsistent chunk objects.

New description:

 The behaviour of a storage server on shares with a corrupt container (bad
 header or inconsistent length) is insufficiently tested. We should
 simulate various kinds of container corruption (also on a subset of shares
 in a shareset that has more than one share), to test that the correct
 errors are raised.

 See for example [https://github.com/LeastAuthority/tahoe-
 lafs/commit/fd819cea11599cc274b8e1d72bfce0fffea39296#L3R93 this bug],
 which showed that raising {{{CorruptStoredShareError}}} on an immutable
 share with an inconsistent container length was untested.

 Note that the code and the intended behaviour (see #1566) has changed on
 the cloud branch so that is what we should test. The cloud backend has
 additional failure modes due to missing or inconsistent chunk objects.

--

-- 
Ticket URL: <https://tahoe-lafs.org/trac/tahoe-lafs/ticket/2025#comment:1>
tahoe-lafs <https://tahoe-lafs.org>
secure decentralized storage