https://outerbounds.com/ logo
Join Slack
Powered by
Hi, i'm having an issue to deploy Metaflow in an A...
# ask-metaflow
a
Hi, i'm having an issue to deploy Metaflow in an AKS (Azure) and i'm getting this error: 
<http://ServicePrincipalsClient.BaseClient.Post|ServicePrincipalsClient.BaseClient.Post>(): unexpected status 403 with OData error: Authorization_RequestDenied: When using this permission, the backing application of the service principal being created must in the local tenant
The terraform can't create the service principal, what should I check?
v
did you log in just by running 
az login
before running 
terraform apply
?
a
Yes I did and set the subscription with "az account set --subscription <subscription-id>"
u
Could it be this issue? https://stackoverflow.com/questions/60004010/creating-service-principal-for-azure-cdn-is-failing-with-tenant-permission-error I.e. the az user you are logged in as when running terraform - does it have "Application Administrator" role granted in Active directory?
a
Thanks for the answers. I double checked the AD and the az user that i'm using has only User access. I'd need to get Application Administrator privileges. I requested those privileges as soon as i get them I'm gonna try again
👍 1
u
@astonishing-television-26703 While you are at it, I'd recommend you review these permissions - all will be needed to deploy the stack.
u
a
@User Thanks for the link i'm having a look at it right now
@User thanks for your hints, they were really helpful I have now the cluster up and running with Argo and Metaflow. but i'm facing a new problem. It says waiting for connection. any idea? I can submit my DAGs to the K8s with the flag --with kubernetes and it works perfectly. Looks like the frontend is failing to connect with the backend service
u
Your guess is reasonable. Did you run setup port forwarding?
u
If yes... next I would recommend checking the backend logs. Assuming your k8s creds are ready. Something like this: 
kubectl get pods | grep backend
(this will tell you the pod name for the backend) Then take the POD_NAME, and do 
kubectl logs POD_NAME
u
(this is because of the 500 status code).
a
I ran the script included in the github repo to forward the ports and somehow i was not working well. but at the end and after several attempts it seems to work. Thanks for your help. Now for me is time to understand Argo
10 Views
Open in Slack
PreviousNext
Powered by