Create a GPU enable Jupyter Notebook with both Isilon and DirectPV volumes

Bug #2008923 reported by Narinder Gupta
10
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Kubeflow-bundle
Invalid
Undecided
Unassigned

Bug Description

Create a GPU enable Jupyter Notebook with both Isilon and DirectPV volumes

Failed with error:or:
{
  "object": {
    "kind": "Notebook",
    "namespace": "guillermo-aure",
    "name": "kubeflow-deployment-validation",
    "uid": "e2deca99-a768-4de4-9274-ef35ff1efb44",
    "apiVersion": "kubeflow.org/v1beta1",
    "resourceVersion": "90644638"
  },
  "reason": "FailedCreate",
  "message": "Reissued from statefulset/kubeflow-deployment-validation: create Pod kubeflow-deployment-validation-0 in StatefulSet kubeflow-deployment-validation failed error: Internal error occurred: failed calling webhook \"namespace.sidecar-injector.istio.io\": failed to call webhook: Post \"https://istiod.k8s.svc:443/inject?timeout=10s\": service \"istiod\" not found"

Revision history for this message
Andrew Scribner (ca-scribner) wrote :

It appears the MutatingWebhook is pointing to a service in a non-existent namespace. We see it calling "istiod.k8s.svc", which would be the istiod service in the k8s namespace. I think this should be "istiod.kubeflow.svc". This was also seen to block creation of all pods in the user's namespace, including the ones automatically created by the kfp-profile-controller in each user namespace

As a test, we manually removed the "istio-injection: enabled" label on the namespace being tested, and with that removed Notebooks and pods start correctly. So something is misconfigured with the webhook for istio sidecar injection and that is the cause of problems

Revision history for this message
Andrew Scribner (ca-scribner) wrote :

@narinder can you provide the output of `kubectl get mutatingwebhookconfigurations.admissionregistration.k8s.io istio-sidecar-injector-kubeflow -o yaml`? We didn't see anything unusual on screen, but maybe someone else will spot something.

Revision history for this message
Narinder Gupta (narindergupta) wrote :

It seems we need to cleanup all wenhooks before redeploy the kubeflow cluster. run the below command to do the cleanup.

./istioctl manifest generate -s profile=minimal -s values.global.istioNamespace=kubeflow |
kubectl delete --ignore-not-found=true -f -

kubectl delete mutatingwebhookconfiguration istio-sidecar-injector-kubeflow

then redeploy the kubeflow it works fine.

Changed in kubeflow-bundle:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.