Forum Discussion
Azure VM Agent Status not ready
I have created a red hat openshift private cluster but the VMS are stuck in the state of "agent status not ready."
I have followed these troubleshooting steps:
Linux Virtual Machine Agent Status "Not Ready" - Microsoft Community Hub
However, all of them seem to point to trying to check and see what is on the VM itself. I am unable to do this because I can't SSH into the machine. Has anyone else ran into this issue and been able to resolve it? I am deploying it via CLI as I was not able to do it via GUI for some reason. This is my script:
#az login
az account set --name "accountnamehidden"
#az provider register -n Microsoft.RedHatOpenShift --wait
#az provider register -n Microsoft.Compute --wait
#az provider register -n Microsoft.Storage --wait
#az provider register -n Microsoft.Authorization --wait
$LOCATION= "eastus" # the location of your cluster
$RESOURCEGROUP= "sample-rg" # the name of the resource group where you want to create your cluster
$CLUSTER= "K8sDev1test" # the name of your cluster
$arovnet= "sample-vnet"
$mastersubnet = "k8sDev1-master-ue-snet"
$workersubnet = "k8sDev1-worker-ue-snet"
az aro create --resource-group "samplerg" --vnet-resource-group "sample-vnet-rg" --name $CLUSTER --vnet $arovnet --master-subnet "k8sDev1-master-ue-snet" --worker-subnet "k8sDev1-worker-ue-snet" --apiserver-visibility Private --ingress-visibility Private --fips true --outbound-type UserDefinedRouting --client-id hidden --client-secret hidden
1 Reply
The important detail here is --outbound-type UserDefinedRouting. With UDR, Azure Red Hat OpenShift does not manage Internet egress for you; you are responsible for providing the required outbound path through your firewall/NVA and allowing the endpoints the cluster needs. I would first check az aro show for the provisioning state, then verify the route tables on both master and worker subnets and inspect firewall logs for blocked HTTPS traffic. ARO infrastructure VMs are managed resources, so I would avoid modifying their NICs or disks directly. If provisioning never completes after validating egress, collect the cluster resource ID and deployment/correlation information and raise an Azure support case.
