[tahoe-lafs-trac-stream] [tahoe-lafs] #1689: assertion failure

[tahoe-lafs]

#1689: assertion failure
-------------------------+-------------------------------------------------
     Reporter:  jg71     |      Owner:  nobody
         Type:  defect   |     Status:  new
     Priority:           |  Milestone:  undecided
  critical               |    Version:  1.9.1
    Component:  unknown  |   Keywords:  tahoe-check verify regression
   Resolution:           |  assertion error mutable
Launchpad Bug:           |
-------------------------+-------------------------------------------------

Comment (by warner):

 I've been able to reproduce the error locally. It's weird, the CLI command
 returns the !AssertionError, but nothing is logged by the node. Usually
 it's the other way around: the node notices an error, logs it, recovers by
 using some alternate share, and the CLI command doesn't see anything
 wrong.

 The assertion error is on the `assert self._privkey` line, which means
 that the repair's Publish operation is trying to use a filenode that never
 got a privkey. This can happen when the filenode was created from a
 readcap, or when have a writecap but were unable (or maybe just forgot) to
 fetch the privkey earlier.

 If it depends upon the contents of the directory, then maybe it's really
 depending upon the length of the share.. if something were fetching a
 portion of the share that usually contains the privkey, but didn't for
 really short shares (empty directories), that might explain it. I'll look
 earlier in the repair process to see where the privkey is usually fetched,
 and if there's any code to complain if that fails.

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