Created attachment 1502279 [details] Node log Description of problem: Failed to deploy hostpath driver with CSI operator on https://github.com/openshift/csi-operator Version-Release number of selected component (if applicable): openshift v4.0.0-0.40.0 kubernetes v1.11.0+d4cacc0 How reproducible: Always Steps to Reproduce: 1. Follow the steps to deploy csi operator and hostpath driver 2. oc apply -f deploy/prerequisites (as admin and below) 3. oc apply -f deploy/operator.yaml 4. oc apply -f deploy/samples/hostpath.yaml Actual results: All the pods created in default project are CrashLoopBackOff # oc get pods NAME READY STATUS RESTARTS AGE hostpath-controller-7d8b7468c8-l9q4j 3/4 CrashLoopBackOff 10 13m hostpath-node-2nnjg 2/3 CrashLoopBackOff 10 13m hostpath-node-89kr5 2/3 CrashLoopBackOff 9 13m hostpath-node-rb25c 2/3 CrashLoopBackOff 9 13m hostpath-node-vzqbk 2/3 CrashLoopBackOff 9 13m Will attach all pods ouputs yaml and described info Expected results: All pods are running and operator can deploy hostpath driver successfully Node Log (of failed PODs): Attached Additional info:
Created attachment 1502280 [details] ControllerYaml
Created attachment 1502281 [details] Describe controller pod
Created attachment 1502282 [details] Driver Yaml
Created attachment 1502283 [details] Describe driver pod
Actually, the image names in internal/external registry are different, it is inconsistent at the moment. In long tern, it can confusing users.
Indeed, liveness probe can't access driver socket if the driver runs as privileged container. Fix: https://github.com/openshift/csi-operator/pull/40
We are not going to support csi-operator in 4.0, I just try to deploy the hostpath driver from step by step, the pods are running well. $ oc get clusterversion NAME VERSION AVAILABLE PROGRESSING SINCE STATUS version 4.0.0-0.nightly-2019-02-10-115019 True False 6h Cluster version is 4.0.0-0.nightly-2019-02-10-115019 $ uname Linux $ cat /etc/redhat-release Red Hat CoreOS release 4.0 $ oc get pods NAME READY STATUS RESTARTS AGE csi-operator-cf8dd4fb-zczn9 1/1 Running 0 8m48s hostpath-controller-6bfddc9f97-j5cnc 4/4 Running 0 6m hostpath-node-lct28 3/3 Running 0 6m hostpath-node-sh7fr 3/3 Running 0 6m hostpath-node-t828m 3/3 Running 0 6m
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory, and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2019:0758