Bug #17355

[keepstore] incorrectly reports the value of ReadOnly for a volume when starting up

Added by Ward Vandewege 2 months ago. Updated 2 months ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
-
Target version:
Start date:
02/09/2021
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
Story points:
-
Release relationship:
Auto

Description

Relevant config snippet:

...
      2xpu4-nyw5e-000000000000001:
        AccessViaHosts:
          "http://keep0.2xpu4.arvadosapi.com:25107": {ReadOnly: true}
          "http://keep1.2xpu4.arvadosapi.com:25107": {}
        Driver: S3
...

On the keep0.2xpu4 host, keepstore logs when it starts up:

Feb 06 16:39:27 keep0.2xpu4.arvadosapi.com keepstore[1206]: {"PID":1206,"level":"info","msg":"started volume 2xpu4-nyw5e-000000000000001 (s3-bucket:\"2xpu4-nyw5e-000000000000001-volume\"), ReadOnly=false","time":"2021-02-06T16:39:27.598868359Z"}

Subtasks

Task #17356: review 17355-report-volume-ReadOnly-correctlyResolvedWard Vandewege

Associated revisions

Revision 3639e67a
Added by Ward Vandewege 2 months ago

Merge branch '17355-report-volume-ReadOnly-correctly'

closes #17355

Arvados-DCO-1.1-Signed-off-by: Ward Vandewege <>

History

#1 Updated by Ward Vandewege 2 months ago

  • Status changed from New to In Progress

#2 Updated by Ward Vandewege 2 months ago

  • Description updated (diff)

#3 Updated by Ward Vandewege 2 months ago

  • Subject changed from [keepstore] should not lie about the value of ReadOnly for the volume when starting up to [keepstore] incorrectly reports the value of ReadOnly for a volume when starting up

#4 Updated by Ward Vandewege 2 months ago

Ready for review at 279dd72bcd41f38e4bcd9ee87d7e8803903f4bca on branch 17355-report-volume-ReadOnly-correctly

#5 Updated by Lucas Di Pentima 2 months ago

LGTM, thanks!

#6 Updated by Ward Vandewege 2 months ago

  • Release set to 37

#7 Updated by Ward Vandewege 2 months ago

  • Status changed from In Progress to Resolved

Also available in: Atom PDF