upstream deployment: olm pod keeps crashing about operator-lifecycle-manager HOT 6 CLOSED

@smanpathak That's actually the olm-operator itself. Looks like there's a mismatch between the deployment manifest and the image it references. We'll get to this soon. Thanks for pointing it out.

from operator-lifecycle-manager.

Can confirm, this is happening for me, too

from operator-lifecycle-manager.

Same here on fresh minikube running k8s v1.13.5

from operator-lifecycle-manager.

On a side note, the quickstart/olm.yaml has the correct image.
User kubectl create -f deploy/upstream/quickstart/olm.yaml to install OLM.

from operator-lifecycle-manager.

Hi,

I'm experiencing the same problem. I'm on an OpenShift 3.11 installation and I also see the same error.
In my case I deployed the OKD manifests (and not the upstream ones) located in: deploy/okd/manifests/0.8.1

The contents of the containers of the OLM operator in 0000_50_olm_06-olm-operator.deployment.yaml are:

       containers:
        - name: olm-operator
          command:
          - /bin/olm
          args:
          - -writeStatusName
          - operator-lifecycle-manager
          image: quay.io/coreos/olm@sha256:995a181839f301585a0e115c083619b6d73812c58a8444d7b13b8e407010325f

The SHA256 of quay.io/coreos/olm@sha256:995a181839f301585a0e115c083619b6d73812c58a8444d7b13b8e407010325f corresponds to the 0.8.1 tag in quay.

To discard any problems with Kubernetes/OpenShift I manually downloaded the quay.io/coreos/olm:0.8.1 image and executed the same command and arguments:

msoriano@localhost:~$ docker run -it quay.io/coreos/olm:0.8.1 olm -writeStatusName operator-lifecycle-manager
flag provided but not defined: -writeStatusName
Usage of olm:
  -alsologtostderr
    	log to standard error as well as files
  -debug
    	use debug log level
  -interval duration
    	wake up interval (default 5m0s)
  -kubeconfig string
    	absolute path to the kubeconfig file
  -log_backtrace_at value
    	when logging hits line file:N, emit a stack trace
  -log_dir string
    	If non-empty, write log files in this directory
  -logtostderr
    	log to standard error instead of files
  -stderrthreshold value
    	logs at or above this threshold go to stderr
  -v value
    	log level for V logs
  -version
    	displays olm version
  -vmodule value
    	comma-separated list of pattern=N settings for file-filtered logging
  -watchedNamespaces -watchedNamespaces=""
    	comma separated list of namespaces for olm operator to watch. If not set, or set to the empty string (e.g. -watchedNamespaces=""), olm operator will watch all namespaces in the cluster.

The -writeStatusName flag seems to not be available in that image version.

from operator-lifecycle-manager.

We've published a new upstream release which should fix these issues for you.

from operator-lifecycle-manager.