Description of problem: Add the following instance types to azure_instance_types list[1]: - Standard_D8s_v5 - Standard_E8s_v5 - Standard_E16s_v5 Version-Release number of selected component (if applicable): OCP 4.8 Steps to Reproduce: 1. Migrate worker/infra nodes to above mentioned (missing) v5 instance types 2. "Failed to set autoscaling from zero annotations, instance type unknown" Actual results: - "Failed to set autoscaling from zero annotations, instance type unknown" - New v5 instance types not officially tested/supported Expected results: The new instance types are available in the azure_instance_types list[1] and no errors/warnings are observed after migrating: - Standard_D8s_v5 - Standard_E8s_v5 - Standard_E16s_v5 Additional info: The related v4 instance types are already available[1] - I suspect adding the mentioned v5 instance types is a minor update: - Standard_D8s_v4 - Standard_E8s_v4 - Standard_E16s_v4 1) azure_instance_types.go https://github.com/openshift/cluster-api-provider-azure/blob/release-4.8/pkg/cloud/azure/actuators/machineset/azure_instance_types.go
Hi Sudha, I know it's a RFE and therefore has low-prio, but do we have a rough estimate on when this might be added? Is there a rough interval from past experience? Thanks
I created the following RFE in Jira: [RFE] Add new Azure instance types to the official "tested/supported" list https://issues.redhat.com/browse/RFE-2896
Moving this to the cloud compute team. I initially mis-triaged this thinking this was asking for a docs update to our supported instance types list. Apologies for the delay.
We need to spend some time to get this data dynamically from Azure rather than storing it within a list, will see if we can prioritise this in the near future
I believe https://bugzilla.redhat.com/show_bug.cgi?id=2108647 should have resolved this issue. QE, could you please verify that the scaling from zero information is set correctly on the above instance types and that the annotation log messages are no longer present
Blocked by https://issues.redhat.com/browse/OCPBUGS-2121
Verfied, annotations are set correctly, autoscaler log no error. 4.12.0-0.nightly-2022-10-07-215539 Standard_D8s_v5: annotations: autoscaling.openshift.io/machineautoscaler: openshift-machine-api/machineautoscaler-c machine.openshift.io/GPU: "0" machine.openshift.io/cluster-api-autoscaler-node-group-max-size: "3" machine.openshift.io/cluster-api-autoscaler-node-group-min-size: "0" machine.openshift.io/memoryMb: "32768" machine.openshift.io/vCPU: "8" Standard_E8s_v5: annotations: autoscaling.openshift.io/machineautoscaler: openshift-machine-api/machineautoscaler-c machine.openshift.io/GPU: "0" machine.openshift.io/cluster-api-autoscaler-node-group-max-size: "3" machine.openshift.io/cluster-api-autoscaler-node-group-min-size: "0" machine.openshift.io/memoryMb: "65536" machine.openshift.io/vCPU: "8" Standard_E16s_v5: annotations: autoscaling.openshift.io/machineautoscaler: openshift-machine-api/machineautoscaler-c machine.openshift.io/GPU: "0" machine.openshift.io/cluster-api-autoscaler-node-group-max-size: "3" machine.openshift.io/cluster-api-autoscaler-node-group-min-size: "0" machine.openshift.io/memoryMb: "131072" machine.openshift.io/vCPU: "16"
Does not need docs as it is basically a duplicate of https://bugzilla.redhat.com/show_bug.cgi?id=2108647
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
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 120 days