Hide Forgot
Description of problem: This is a just a duplicate of https://jira.coreos.com/browse/MC-472. This is the same underlying cause as MC-412. The service-ca.crt isn't in the pod, and recent changes have adjusted how we access the file so now the metering pod fails immediately when the file doesn't exist instead of using the wrong certificate like it did previously. Version-Release number of selected component (if applicable): Client Version: version.Info{Major:"4", Minor:"0+", GitVersion:"v4.0.0-0.185.0", GitCommit:"e883da29bc", GitTreeState:"", BuildDate:"2019-02-25T13:48:37Z", GoVersion:"", Compiler:"", Platform:""} Server Version: version.Info{Major:"1", Minor:"12+", GitVersion:"v1.12.4+e883da29bc", GitCommit:"e883da29bc", GitTreeState:"clean", BuildDate:"2019-02-25T13:47:14Z", GoVersion:"go1.10.3", Compiler:"gc", Platform:"linux/amd64"} metering version: pruan@desktop ~/workspace/operator-metering (master)$ git rev-parse HEAD bc9f8bca2307b220b5e1bcea4af5a705c0f2bbc7 How reproducible: always Steps to Reproduce: 1. git clone https://github.com/operator-framework/operator-metering 2. run the manual installation script ./hack/openshift-install.sh 3. Actual results: pruan@dhcp-91-104 ~/workspace/operator-metering (master)$ oc get pods NAME READY STATUS RESTARTS AGE hdfs-datanode-0 1/1 Running 0 14m hdfs-namenode-0 1/1 Running 0 14m hive-metastore-0 1/1 Running 0 14m hive-server-0 1/1 Running 1 14m metering-operator-7bc7d5dc69-wn8hl 2/2 Running 0 15m presto-coordinator-69c4c79ddd-wrt9k 1/1 Running 0 14m reporting-operator-6fb959fd77-tc8xn 0/1 CrashLoopBackOff 6 6m43s time="2019-03-01T06:31:34Z" level=fatal msg="error occurred while the reporting-operator was running" app=metering error="stat /var/run/secrets/kubernetes.io/serviceaccount/service-ca.crt: no such file or directory" Expected results: Additional info:
waiting for nightly build that has this merged PR https://github.com/openshift/cluster-kube-controller-manager-operator/pull/178
Hi Peter,could you help check if it could be verified?
verified. I metering can be installed now and the service-ca.cert file is present