-
Notifications
You must be signed in to change notification settings - Fork 3.4k
Option to Bypass Pre-Flight Check in Azure CLI for ARO #27719
Copy link
Copy link
Open
Labels
AROaz aro (Azure Redhat OpenShift)az aro (Azure Redhat OpenShift)Auto-AssignAuto assign by botAuto assign by botAuto-ResolveAuto resolve by botAuto resolve by botService AttentionThis issue is responsible by Azure service team.This issue is responsible by Azure service team.act-codegen-extensibility-squadbugThis issue requires a change to an existing behavior in the product in order to be resolved.This issue requires a change to an existing behavior in the product in order to be resolved.customer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues that are reported by GitHub users external to the Azure organization.
Description
Metadata
Metadata
Assignees
Labels
AROaz aro (Azure Redhat OpenShift)az aro (Azure Redhat OpenShift)Auto-AssignAuto assign by botAuto assign by botAuto-ResolveAuto resolve by botAuto resolve by botService AttentionThis issue is responsible by Azure service team.This issue is responsible by Azure service team.act-codegen-extensibility-squadbugThis issue requires a change to an existing behavior in the product in order to be resolved.This issue requires a change to an existing behavior in the product in order to be resolved.customer-reportedIssues that are reported by GitHub users external to the Azure organization.Issues that are reported by GitHub users external to the Azure organization.
Describe the bug
The recent Azure CLI version 2.52.0 release introduced a pre-flight check for Azure Red Hat OpenShift (ARO). It seems that there's no option available to skip this check at the moment. This issue is currently blocking the provisioning of clusters that leverage specific preview features, notably the Bring Your Own Network Security Group (BYO NSG). The inability to bypass this pre-flight check is particularly problematic since it affects otherwise valid configurations that are not officially supported yet. Adding a feature to skip this check would be extremely useful. Given that this situation is hindering installations that previously succeeded, I am reporting this as a bug rather than a feature request. I believe this constitutes a regression from earlier functionality.
Related command
az aro create
Errors
E.g. the command fails when there are pre-existing NSGs in a subnet, even if the BYO NSG preview feature is activated
Issue script & Debug output
N/A
Expected behavior
Provide a parameter to skip the pre-flight check
Environment Summary
azure-cli >= 2.52.0
Additional context
No response