Bug #9678: [Crunch2] [Workbench] container_request log tab is empty, even when the container log tab shows information - Arvados

Custom queries

All assigned issues
All issues assigned for grooming
My issues for grooming
My issues for grooming (no story pts)
Prioritized open issues

Actions

Copy link

Bug #9678

closed

[Crunch2] [Workbench] container_request log tab is empty, even when the container log tab shows information

Added by Radhika Chippada over 8 years ago. Updated over 8 years ago.

Status:

Resolved

Priority:

Normal

Assigned To:

Radhika Chippada

Category:

Target version:

2016-08-17 sprint

Story points:

1.0

Release:

Crunch v2

Release relationship:

Auto

Subtasks 1 (0 open — 1 closed)

Task #9728: Review branch 9678-container-request-log-tab

Resolved

Radhika Chippada

08/11/2016

Actions

Related issues 2 (0 open — 2 closed)

	Related to Arvados - Bug #9679: [Crunch2] Provide feedback when a container is submitted to slurm but does not run	Resolved	Tom Clegg	07/29/2016			Actions
	Related to Arvados - Bug #9799: [Crunch2] Ensure live logs for containers are accessible to non-admin users	Resolved	Tom Clegg	08/17/2016			Actions

Issue # Delay: days Cancel

History
Notes
Property changes
Associated revisions

Actions

Copy link

Updated by Radhika Chippada over 8 years ago

When I go to a container_request's Log tab, I see an empty "Recent logs" area. However, if I were to click on it's container link and go to the Log tab for that, I see logs in there. The container request in this case should show the container's logs instead of a empty area?

https://workbench.9tee4.arvadosapi.com/container_requests/9tee4-xvhdp-q5bp2u1irjaoqec#Log

https://workbench.9tee4.arvadosapi.com/containers/9tee4-dz642-wzr7g7s0g0sw0nr#Log

Actions

Copy link