Bug 1882608
| Summary: | Spot instance not getting created on AzureGovCloud | ||
|---|---|---|---|
| Product: | OpenShift Container Platform | Reporter: | Milind Yadav <miyadav> |
| Component: | Cloud Compute | Assignee: | Alexander Demicev <ademicev> |
| Cloud Compute sub component: | Other Providers | QA Contact: | Milind Yadav <miyadav> |
| Status: | CLOSED ERRATA | Docs Contact: | |
| Severity: | medium | ||
| Priority: | medium | CC: | ademicev, mimccune, zhsun |
| Version: | 4.6 | ||
| Target Milestone: | --- | ||
| Target Release: | 4.7.0 | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | Doc Type: | No Doc Update | |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-02-24 15:21:14 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
Milind Yadav
2020-09-25 06:58:19 UTC
@Milind, I don't think I have access to GovCloud to try to reproduce this, could you try again but without setting a maxPrice, just use `spotVMOptions: {}` instead? Would be good to know if it is related to any Spot VM or just if there is a maxPrice
@joel - tried as you suggested :
providerSpec:
value:
spotVMOptions: {}
Events:
Type Reason Age From Message
---- ------ ---- ---- -------
Warning FailedCreate 18s azure-controller InvalidConfiguration: failed to reconcile machine "miyadav-az-zzlxl-worker-spot-fzd4r": failed to create vm miyadav-az-zzlxl-worker-spot-fzd4r: failure sending request for machine miyadav-az-zzlxl-worker-spot-fzd4r
I'm aware that on AWS, their GovCloud didn't support spot instances for a very long time, though I believe it does now. I wonder if Azure just doesn't support creating spot instances on the GovCloud tenant. I think we will need to do some research and try to work out if they should be supported on GovCloud or not. I'm not able to launch any spot instance using Azure GovCloud console. I think spot instances are not supported in GovCloud. I spoke with Alex yesterday who confirmed (as per https://bugzilla.redhat.com/show_bug.cgi?id=1882608#c4) that when trying to create an instance in Azure GovCloud, independently of OCP, that the same error occurs. Since we are aware that spot instances can be created in other regions, I suspect that the issue here is that Azure does not support Spot Instances in this region. I've asked Alex to try and confirm if this is the case and hopefully we will have an answer to this question during the next sprint. If this is the case, we may be able to improve the error message that we return to improve UX. Additionally we should ensure that the docs team are aware and can add a note that this region doesn't support spot (if that is the case). Spot instances are most likely not supported on GovCloud. I've reached out to some folks from Microsoft to try and get an answer as to whether these are supported or not. My suggestion is that we add a warning via a webhook if we can see that the region is GovCloud and Spot VMs are requested, for example "Warning: Spot VMs may not be supported in this region". I will update this issue if I get a response. @ademicev I've had no response from MS about this. I think the route to closing this issue should be adding a webhook warning when spot instances are requested in the GovCloud region, something akin to "Warning: Spot VMs may not be supported in this region". Could you create a PR to add that please? the PR associated with this has all the necessary labels and is currently waiting on CI to pass Validated on:
[miyadav@miyadav ~]$ oc get clusterversion
NAME VERSION AVAILABLE PROGRESSING SINCE STATUS
version 4.7.0-0.ci-2020-12-08-014807 True False 30m Cluster version is 4.7.0-0.ci-2020-12-08-014807
Steps:
1.Create machineset to provision spot instance , refer below
.
.
spec:
metadata: {}
providerSpec:
value:
spotVMOptions:
maxPrice: 0.225
.
.
Actual & Expected - machineset created successfully
2.Monitor logs ( oc logs -f machine-controller-pod -c machine-controller
Actual & Expected -
I1208 05:03:35.631580 1 actuator.go:168] Updating machine miyadav608az-zvd4x-worker-usgovvirginia-s-v9tlq
I1208 05:03:35.894049 1 machine_scope.go:144] miyadav608az-zvd4x-worker-usgovvirginia-s-v9tlq: status unchanged
I1208 05:03:35.894084 1 machine_scope.go:144] miyadav608az-zvd4x-worker-usgovvirginia-s-v9tlq: status unchanged
I1208 05:03:35.894089 1 machine_scope.go:160] miyadav608az-zvd4x-worker-usgovvirginia-s-v9tlq: patching machine
W1208 05:03:35.907643 1 warnings.go:67] spot VMs may not be supported when using GovCloud region
Additional info:
Moved to Verified
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 (Moderate: OpenShift Container Platform 4.7.0 security, bug fix, and enhancement update), 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/RHSA-2020:5633 |