Bug 1835179

Summary:	Add E2E validation for Spot Insances on AWS
Product:	OpenShift Container Platform	Reporter:	Joel Speed <jspeed>
Component:	Cloud Compute	Assignee:	Joel Speed <jspeed>
Cloud Compute sub component:	Other Providers	QA Contact:	sunzhaohua <zhsun>
Status:	CLOSED ERRATA	Docs Contact:
Severity:	low
Priority:	unspecified
Version:	4.5
Target Milestone:	---
Target Release:	4.5.0
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Enhancement
Doc Text:	Feature: Adds end to end testing for launching spot instances on AWS Reason: To validate that we aren't breaking features in the future Result: Tests currently pass assuming a spot instance can be created	Story Points:	---
Clone Of:		Environment:
Last Closed:	2020-07-13 17:38:25 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Joel Speed 2020-05-13 10:25:20 UTC

Description of problem:

We want to have E2E validation for running Spot instances on AWS to make sure that we don't break the functionality that we have introduced


Version-Release number of selected component (if applicable):
4.5

How reproducible:


Steps to Reproduce:
1.
2.
3.

Actual results:


Expected results:


Additional info:

Comment 3 sunzhaohua 2020-05-26 05:49:39 UTC

Move to verified, because spot instace features are tested and no problems were found, these 2 cases are passed.
https://deck-ci.apps.ci.l2s4.p1.openshiftapps.com/view/gs/origin-ci-test/pr-logs/pull/openshift_cluster-api-actuator-pkg/149/pull-ci-openshift-cluster-api-actuator-pkg-master-e2e-aws-operator/565
[Feature:Machines] Running on Spot should deploy a termination handler pod to each instance
[Feature:Machines] Running on Spot should label the Machine specs as interruptible

Comment 4 errata-xmlrpc 2020-07-13 17:38:25 UTC

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://access.redhat.com/errata/RHBA-2020:2409