Project

General

Profile

Actions

Bug #18562

closed

[api] should not change the preemptible flag across the board

Added by Ward Vandewege about 1 year ago. Updated 10 months ago.

Status:
Resolved
Priority:
Normal
Assigned To:
Category:
-
Target version:
Start date:
12/23/2021
Due date:
% Done:

100%

Estimated time:
(Total: 0.00 h)
Story points:
-
Release relationship:
Auto

Description

The RailsAPI changes applies the default config value for the preemptible flag whenever a container record is loaded. This causes problems when the config value is changed after a container record has been created and before it is done.

Case in point, if a-d-c tries to cancel (sends State=Cancelled) a container that was created when the config said `UsePreemptible: true` and meanwhile the config is changed to `UsePreemptible: false`, RailsAPI fails validation and returns a 422 on the cancel request.

RailsAPI should only set/change the `Preemptible` flag in one place, maybe when the container is created or when it is committed.


Subtasks 1 (0 open1 closed)

Task #18567: Review 18562-preemptibleResolvedWard Vandewege12/23/2021

Actions

Related issues

Related to Arvados - Feature #18596: Config option to enable preemptible variants of all instance typesResolvedTom Clegg03/21/2022

Actions
Related to Arvados Epics - Story #18179: Better spot instance supportIn Progress03/01/202204/30/2023

Actions
Actions

Also available in: Atom PDF