#618 closed defect (invalid)
tahoe backup crash during second run
| Reported by: | francois | Owned by: | |
|---|---|---|---|
| Priority: | major | Milestone: | undecided |
| Component: | code-frontend-cli | Version: | 1.3.0 |
| Keywords: | Cc: | ||
| Launchpad Bug: |
Description
An exception is raised by tahoe node during the second run of tahoe backup.
<type 'exceptions.AttributeError?'>: NewDirectoryNode? instance has no attribute 'replace_me_with_a_childcap'
It seems related to the last step of the backup process where the Latest/ directory is linked to the latest Archives/timestamp/.
Attached html file contains more details.
Attachments (1)
Change History (4)
Changed at 2009-02-10T19:30:32Z by francois
comment:1 Changed at 2009-02-10T19:33:07Z by francois
comment:2 Changed at 2009-02-10T20:04:11Z by francois
- Resolution set to invalid
- Status changed from new to closed
Well, it is certainly a normal incompatibility issue between the latest CLI and an older node.
The recent CLI running against a recent node doesn't raise any exception.
comment:3 Changed at 2009-02-10T20:57:15Z by warner
Yeah, that error is the result of a bug that was fixed 28-Oct-2008, in change a5aebf0cbd066cf2, such that the webapi interface used by that last step of backup just didn't work.
I'll add a note to the NEWS file to indicate that 'tahoe backup' requires a 1.3.0 client node, since the 1.2.0 webapi still had this bug.
The incriminated node is actually on the production allmydata.com grid.