Feature #8363
closedcrunch-run scans arv-mount logging for errors
Description
Crunch-run should check the logs of arv-mount for known error patterns. If found, it posts a warning to "runtime_status" to the container record there was an arv-mount error.
The patterns to look for are
- "Keep write error"
- "Block not found error"
- "Unhandled exception during FUSE operation"
Updated by Brett Smith about 9 years ago
- Target version set to Arvados Future Sprints
Updated by Peter Amstutz over 5 years ago
- Related to Bug #15727: [FUSE] Unhandled exception while getting discovery doc added
Updated by Peter Amstutz about 4 years ago
- Target version changed from Arvados Future Sprints to 2021-03-03 sprint
Updated by Peter Amstutz about 4 years ago
- Description updated (diff)
- Subject changed from [FUSE] arv-mount exits non-zero if any I/O errors were returned to crunch-run scans arv-mount logs for errors
Updated by Peter Amstutz about 4 years ago
- Subject changed from crunch-run scans arv-mount logs for errors to crunch-run scans arv-mount logging for errors
Updated by Peter Amstutz about 4 years ago
- Assigned To changed from Lucas Di Pentima to Nico César
Updated by Peter Amstutz about 4 years ago
- Target version changed from 2021-03-03 sprint to 2021-03-17 sprint
Updated by Peter Amstutz almost 4 years ago
- Target version changed from 2021-03-17 sprint to 2021-03-31 sprint
Updated by Nico César almost 4 years ago
- Target version changed from 2021-03-31 sprint to 2021-04-14 sprint
Updated by Peter Amstutz almost 4 years ago
- Assigned To changed from Nico César to Lucas Di Pentima
Updated by Peter Amstutz almost 4 years ago
- Target version changed from 2021-04-14 sprint to 2021-04-28 bughunt sprint
Updated by Peter Amstutz almost 4 years ago
- Target version changed from 2021-04-28 bughunt sprint to 2021-05-12 sprint
Updated by Lucas Di Pentima almost 4 years ago
- Target version changed from 2021-05-12 sprint to 2021-05-26 sprint
Updated by Peter Amstutz almost 4 years ago
- Assigned To changed from Lucas Di Pentima to Nico César
Updated by Nico César almost 4 years ago
- Status changed from New to In Progress
Updated by Peter Amstutz almost 4 years ago
- Target version changed from 2021-05-26 sprint to 2021-06-09 sprint
Updated by Peter Amstutz over 3 years ago
- Target version changed from 2021-06-09 sprint to 2021-06-23 sprint
Updated by Peter Amstutz over 3 years ago
- Target version changed from 2021-06-23 sprint to 2021-07-07 sprint
Updated by Peter Amstutz over 3 years ago
- Target version changed from 2021-07-07 sprint to 2021-07-21 sprint
Updated by Peter Amstutz over 3 years ago
- Target version changed from 2021-07-21 sprint to 2021-08-04 sprint
Updated by Peter Amstutz over 3 years ago
- Status changed from In Progress to New
Updated by Peter Amstutz over 3 years ago
- Target version changed from 2021-08-04 sprint to 2021-09-01 sprint
Updated by Peter Amstutz over 3 years ago
- Target version changed from 2021-09-01 sprint to 2021-09-15 sprint
Updated by Peter Amstutz over 3 years ago
- Target version changed from 2021-09-15 sprint to 2021-09-29 sprint
Updated by Tom Clegg over 3 years ago
8363-fuse-warnings @ ce84723a4704a766f7e0dc3c61896733bf94f838 -- developer-run-tests: #2700
Updated by Lucas Di Pentima over 3 years ago
- Just one question: Do you think it would be useful to provide more information (for example on
runtime_status[warningDetail]
) by adding the entire txt string that matched the pattern?
The rest LGTM
Updated by Lucas Di Pentima over 3 years ago
Update: Jenkins failed at developer-run-tests-remainder: #2807 /console
Updated by Lucas Di Pentima over 3 years ago
While refreshing my memory about runtime_status
I realized that we mistakenly list errorDetails
and warningDetails
in plural in the docs for runtime_status
. The correct ones are singular.
Updated by Tom Clegg over 3 years ago
Good points.
8363-fuse-warnings @ 517896bc3c34365cc4d4eb54d36db6b439e994d0 -- developer-run-tests: #2703
- include entire matching log entry as warningDetail
- fix spelling of errorDetail/warningDetail in docs
- update tests to match new ArvMountCmd semantics
Updated by Tom Clegg over 3 years ago
- Status changed from In Progress to Resolved
Applied in changeset arvados-private:commit:arvados|c9aaa4d329b08c8b1c8cfd566c5282ab57e97f05.