Actions
Bug #13168
closed
[API] state/priority-change triggers should not change container request modified_by_user_uuid to root
Status:
Resolved
Priority:
Normal
Assigned To:
Category:
-
Target version:
Start date:
03/29/2018
Due date:
% Done:
100%
Estimated time:
(Total: 0.00 h)
Story points:
-
Release:
Release relationship:
Auto
Description
For example, when a container finishes, each container request with a matching container_uuid gets finalized (log, output, and state are updated). Currently, the finalizing mechanism inadvertently updates the container request's "modified by user" attribute to root. It should be left alone.
Updated by Tom Clegg almost 7 years ago
- Related to Story #10511: [Crunch2] [API] Specify which user's credentials should be used by a container added
Updated by Tom Morris almost 7 years ago
- Target version set to 2018-04-11 Sprint
Updated by Tom Clegg over 6 years ago
- Has duplicate Feature #13279: [Crunch v2] add job field in crunch v2 to show who created job added
Updated by Lucas Di Pentima over 6 years ago
- Assigned To set to Lucas Di Pentima
Updated by Lucas Di Pentima over 6 years ago
- Status changed from New to In Progress
Updated by Lucas Di Pentima over 6 years ago
Updates at 378eeb13b - branch 13168-cr-modified-user
Test run: https://ci.curoverse.com/job/developer-run-tests/672/
Updated by Peter Amstutz over 6 years ago
I did a test running a container, the container request modified_at had the right user after it finished, so this looks LGTM.
Updated by Lucas Di Pentima over 6 years ago
- Status changed from In Progress to Resolved
Applied in changeset arvados|2baac8a6702551064b065f752f75a9b40dbec0f5.
Updated by Tom Clegg about 6 years ago
- Related to Bug #14595: [API] logs.event_at has wrong timestamp added
Actions