Bug 2108647
Summary: | [azure] Standard_D2s_v3 as worker failed by “accelerated networking not supported on instance type” | ||
---|---|---|---|
Product: | OpenShift Container Platform | Reporter: | MayXu <maxu> |
Component: | Cloud Compute | Assignee: | Radek Maňák <rmanak> |
Cloud Compute sub component: | Other Providers | QA Contact: | sunzhaohua <zhsun> |
Status: | CLOSED ERRATA | Docs Contact: | Jeana Routh <jrouth> |
Severity: | medium | ||
Priority: | medium | CC: | aarapov, daliu, dhuynh, gpei, jialiu, rmanak |
Version: | 4.11 | ||
Target Milestone: | --- | ||
Target Release: | 4.12.0 | ||
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | Doc Type: | Bug Fix | |
Doc Text: |
* Previously, when Azure added new instance types and enabled accelerated networking support on instance types that previously did not have it, the list of Azure instances in the machine controller became outdated. As a result, the machine controller could not create machines with instance types that did not previously support accelerated networking, even if they support this feature on Azure. With this release, the required instance type information is retrieved from Azure API before the machine is created to keep it up to date and the machine controller is able to create machines with new and updated instance types. This fix also applies to any instance types that are added in the future. (link:https://bugzilla.redhat.com/show_bug.cgi?id=2108647[*BZ#2108647*])
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2023-01-17 19:53:06 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: | |||
Bug Depends On: | |||
Bug Blocks: | 2115852 |
Description
MayXu
2022-07-19 15:39:07 UTC
Going to ask a member of the team to look further into this, we understand the issue and know what it is we need to do. A dynamic check rather than the static list. Will post updates once we've started working on it. I am working on a fix for this. *** Bug 2115852 has been marked as a duplicate of this bug. *** *** Bug 2115851 has been marked as a duplicate of this bug. *** Any update for this issue? Still working on this. I have it in working state, just need to clean it up a bit and make sure there is no regression. Is the workaround for this issue to simply use a different machine type for the worker nodes? The workaround can be found here: https://coreos.slack.com/archives/C68TNFWA2/p1659964442215109?thread_ts=1659925635.953309&cid=C68TNFWA2 Eg: workaround by forcing Accelerated=False in the install-config for the compute nodes. Or change the node type for compute nodes. /bugzilla refresh Oops. Wrong tab, sorry(In reply to Radek Maňák from comment #10) > /bugzilla refresh Sorry, wrong browser tab verified on registry.ci.openshift.org/ocp/release:4.12.0-0.ci-2022-09-13-225342 and registry.ci.openshift.org/ocp/release:4.12.0-0.nightly-2022-09-13-202959 $ az network nic list -g $RG -o json --query "[].[name, enableAcceleratedNetworking]" -o tsv maxu-ac1-bwz6k-master-0-nic True maxu-ac1-bwz6k-master-1-nic True maxu-ac1-bwz6k-master-2-nic True maxu-ac1-bwz6k-worker-eastus1-468jw-nic True maxu-ac1-bwz6k-worker-eastus2-p2pzw-nic True maxu-ac1-bwz6k-worker-eastus3-r4rhf-nic True $ oc get machine -A NAMESPACE NAME PHASE TYPE REGION ZONE AGE openshift-machine-api maxu-ac1-bwz6k-master-0 Running Standard_D4s_v3 eastus 2 39m openshift-machine-api maxu-ac1-bwz6k-master-1 Running Standard_D4s_v3 eastus 3 38m openshift-machine-api maxu-ac1-bwz6k-master-2 Running Standard_D4s_v3 eastus 1 38m openshift-machine-api maxu-ac1-bwz6k-worker-eastus1-468jw Running Standard_D2s_v3 eastus 1 30m openshift-machine-api maxu-ac1-bwz6k-worker-eastus2-p2pzw Running Standard_D2s_v3 eastus 2 30m openshift-machine-api maxu-ac1-bwz6k-worker-eastus3-r4rhf Running Standard_D2s_v3 eastus 3 30m 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.12.0 bug fix and security 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-2022:7399 |