Bug #11470
closed
[API] container_requests#update alternately responds 422 or 404 for no apparent reason
Added by Tom Clegg about 7 years ago.
Updated about 6 years ago.
Description
Seems like a race condition -- perhaps related to permission lookups or other container request updates that are happening at the ~same time?
- Description updated (diff)
11470-update-task-fields LGTM
- Assigned To deleted (
Tom Clegg)
- Target version changed from 2017-04-26 sprint to 2017-05-10 sprint
- Assigned To set to Nico César
- Target version changed from 2017-05-10 sprint to 2017-05-24 sprint
To be reviewed after Roche upgrade
update the clusters with Carlos next weeks and after all updates review the status with him ... there is a pipeline of several incoming changes on their clusters. as follows:
#10111: Provenance graph for container requests - merged - and latest version isn't running in our clusters
#10645: Better display of command / inputs for container requests - merged - and not running in our clusters
RT 321 / #11469: Use temp space outside container - merged - and not running in our clusters
#11626: Propagate slurm errors so they are visible in workbench - in review
RT 355: Efficient loading & rendering of many container requests - in progress
#10112: Improve display of workflow - in progress
-- Also slurm integration improvements for requesting the correct amount of memory and disk.
- Target version changed from 2017-05-24 sprint to Arvados Future Sprints
- Status changed from New to Resolved
- Target version deleted (
Arvados Future Sprints)
Also available in: Atom
PDF
Updated by 
Updated by 
Updated by Tom Morris 
Updated by