Project

General

Profile

Actions

Feature #21133

open

Add diagnostics checks for container log API

Added by Tom Clegg 9 months ago. Updated 5 months ago.

Status:
New
Priority:
Normal
Assigned To:
-
Category:
Deployment
Target version:
Story points:
1.0

Description

If it runs a container, arvados-server diagnostics should
  1. access the container log endpoint while waiting for the container to finish, to make sure it returns a valid response (due to races, it's not necessarily an error if it can't get any actual log data before the container finishes, but it's an error if it receives a 502 error at any point during the container lifecycle, for example).
  2. access the container log endpoint after the container has finished, to make sure the controller→webdav communication works correctly.

It is possible for a cluster to be misconfigured such that logs work only for unfinished containers, or only for finished containers, so diagnostics should do its best to check for both problems.


Related issues

Related to Arvados - Feature #21279: cloudtest command should test connectivity to crunch-run gatewayNewActions
Actions

Also available in: Atom PDF