Opened at 2019-06-12T20:09:09Z
Closed at 2019-06-26T11:57:37Z
#3051 closed defect (fixed)
Storage clients fail, nearly completely, when they encounter a "bad" storage announcement
Reported by: | exarkun | Owned by: | GitHub <noreply@…> |
---|---|---|---|
Priority: | normal | Milestone: | storage economics plugins |
Component: | code | Version: | n/a |
Keywords: | review-needed | Cc: | |
Launchpad Bug: |
Description
I tried putting a weird announcement (relating to a possible new feature) into servers.yaml. load_static_servers really didn't like it and raised an exception which made it all the way up to the top level and got logged. It stopped all the rest of client initialization and rendered the client totally useless (but still running).
Instead, weird announcements should be logged, marked as weird, but should not hurt initialization, startup, and normal operation of anything else that's configured.
Change History (3)
comment:1 Changed at 2019-06-13T01:02:13Z by exarkun
- Milestone changed from undecided to storage economics plugins
comment:2 Changed at 2019-06-13T16:55:45Z by exarkun
- Keywords review-needed added
comment:3 Changed at 2019-06-26T11:57:37Z by GitHub <noreply@…>
- Owner set to GitHub <noreply@…>
- Resolution set to fixed
- Status changed from new to closed
In 23e3605/trunk:
Note: See
TracTickets for help on using
tickets.
https://github.com/tahoe-lafs/tahoe-lafs/pull/621