Actions
Idea #18860
closedDisplay count of container attempts and make it easy to access past logs
Status:
Resolved
Priority:
Normal
Assigned To:
-
Category:
Workbench2
Target version:
-
Start date:
Due date:
Story points:
-
Description
When a container fails and is restarted due to an infrastructure failure (keep read error, spot instance reclaimed, etc) the process view should make it clear what happened and make it easy to access logs of the failed container attempts.
If container_count > 1 that means something went wrong, it should give a warning that the container has been tried (container_count) times.
Updated by Peter Amstutz almost 3 years ago
- Related to Idea #16945: WB2 Workflows / containers feature parity added
Updated by Peter Amstutz over 2 years ago
- Target version set to 2022-09-14 sprint
Updated by Peter Amstutz over 2 years ago
- Subject changed from Display number of container attempts and make it easy to access past logs to Display count of container attempts and make it easy to access past logs
Updated by Peter Amstutz over 2 years ago
- Target version changed from 2022-09-14 sprint to 2022-09-28 sprint
Updated by Peter Amstutz over 2 years ago
- Target version changed from 2022-09-28 sprint to 2022-10-12 sprint
Updated by Peter Amstutz over 2 years ago
- Target version changed from 2022-10-12 sprint to 2022-10-26 sprint
Updated by Peter Amstutz about 2 years ago
- Target version changed from 2022-10-26 sprint to 2022-11-09 sprint
Updated by Peter Amstutz about 2 years ago
- Target version changed from 2022-11-09 sprint to 2022-11-23 sprint
Updated by Peter Amstutz about 2 years ago
- Target version changed from 2022-11-23 sprint to 2022-12-07 Sprint
Updated by Peter Amstutz about 2 years ago
- Target version changed from 2022-12-07 Sprint to 2022-12-21 Sprint
Updated by Stephen Smith about 2 years ago
- Related to Feature #19093: Process details should display a warning if "container_count" is greater than 1 (meaning it failed and was retried) added
Updated by Peter Amstutz about 2 years ago
- Target version changed from 2022-12-21 Sprint to 2023-02-15 sprint
Updated by Peter Amstutz almost 2 years ago
- Target version changed from 2023-02-15 sprint to Future
Updated by Peter Amstutz almost 2 years ago
- Status changed from New to Resolved
Actions