-
Notifications
You must be signed in to change notification settings - Fork 131
Open
Description
- When we try install the Azure Service Operator using the command provided in the document, the pods deployed in the OpenShift console are not being successfully deployed:
Install the ASO.
helm upgrade --install --devel aso2 aso2/azure-service-operator
--create-namespace
--namespace=azureserviceoperator-system
--set azureSubscriptionID=$AZURE_SUBSCRIPTION_ID
--set azureTenantID=$AZ_TENANT_ID
--set azureClientID=$SERVICE_PRINCIPAL_CLIENT_ID
--set azureClientSecret=$SERVICE_PRINCIPAL_CLIENT_SECRET
Pod crash loop back-off
back-off 5m0s restarting failed container=manager pod=azureserviceoperator-controller-manager-79ff657445-rzkkk_azureserviceoperator-system(e340c746-45b3-47e2-847d-043eb014e942)
CrashLoopBackOff indicates that the application within the container is failing to start properly.
To troubleshoot, view logs and events, then debug in terminal.
- Since the Azure Service Operator (ASO) is not being installed as expected and the pod in the OpenShift console is failing to successfully deploy, when we try to deploy the application, we’re not seeing the expected results as provided in the document and the application isn’t running as expected.

Reactions are currently unavailable
Metadata
Metadata
Assignees
Labels
No labels