Page MenuHomePhabricator

[drydock/aws] Check that the instance started by a spot request is API consistent
AbandonedPublic

Authored by hach-que on Jul 2 2015, 3:12 AM.
Tags
None
Referenced Files
Unknown Object (File)
Tue, Mar 26, 5:51 AM
Unknown Object (File)
Feb 12 2024, 10:43 PM
Unknown Object (File)
Feb 3 2024, 12:19 AM
Unknown Object (File)
Jan 5 2024, 3:37 PM
Unknown Object (File)
Dec 28 2023, 4:55 PM
Unknown Object (File)
Dec 23 2023, 4:48 PM
Unknown Object (File)
Dec 18 2023, 8:12 AM
Unknown Object (File)
Dec 11 2023, 7:40 PM
Subscribers

Details

Reviewers
epriestley
Group Reviewers
Blessed Reviewers
Maniphest Tasks
T2015: Implement Drydock
Summary

Ref T2015. I saw this issue occur in production where a spot instance reported that an instance had been fulfilled, but then when tagging the instance it failed because the instance wasn't visible in the API yet. This adds an API consistency wait to the spot instance section that waits for the instance to become available in the API.

Test Plan

N/A

Diff Detail

Branch
master
Lint
Lint Passed
Unit
Test Failures
Build Status
Buildable 7111
Build 7274: [Placeholder Plan] Wait for 30 Seconds
Build 7273: arc lint + arc unit

Event Timeline

hach-que retitled this revision from to [drydock/aws] Check that the instance started by a spot request is API consistent.
hach-que updated this object.
hach-que edited the test plan for this revision. (Show Details)
hach-que added a reviewer: epriestley.