Skip to content

Latest commit

 

History

History
72 lines (49 loc) · 2.5 KB

troubleshooting.md

File metadata and controls

72 lines (49 loc) · 2.5 KB
Raw

Troubleshooting

This document provides useful information for common errors and their remedies:

Run without CRD applied

Command

$ operator-sdk run local --watch-namespace gcp-project-operator

Error Message

"kubebuilder.source","msg":"if kind is a CRD, it should be installed before calling Start"
panic: no matches for kind "ProjectClaim" in version "gcp.managed.openshift.io/v1alpha1"

goroutine 1 [running]:
main.main()
        FATA[0001] Failed to run operator locally: failed to run operator locally: failed to exec []string{"build/_output/bin/gcp-project-operator-local"}: exit status 2

Explanation

This error message means you have started running the operator locally without having the ProjectClaim custom resource definition applied in the Kubernetes cluster. As a result, kubernetes (and, by extension, the GCP Operator) does not know what a ProjectClaim is.

Solution

This is expected behavior. According to the message from KubeBuilder (which is the one Operators SDK is based upon) the CRDs should be installed before starting the operator. Please type:

$ kubectl create -f deploy/crds/gcp.managed.openshift.io_projectclaims_crd.yaml

Operator does nothing

Command

$ kubectl create -f deploy/crds/gcp.managed.openshift.io_projectclaims_crd.yaml

Logs

{"level":"info","ts":1583866815.154782,"logger":"kubebuilder.controller","msg":"Starting Controller","controller":"projectreference-controller"}
{"level":"info","ts":1583866815.154809,"logger":"kubebuilder.controller","msg":"Starting Controller","controller":"projectclaim-controller"}
{"level":"info","ts":1583866815.254899,"logger":"kubebuilder.controller","msg":"Starting workers","controller":"projectclaim-controller","worker count":1}
{"level":"info","ts":1583866815.254951,"logger":"kubebuilder.controller","msg":"Starting workers","controller":"projectreference-controller","worker count":1}

Explanation

When the SharedIndexInformer caches are synced, then the workers are starting as well. The workers are launching to process the resources. The operator launches one worker per controller, thus MaxConcurrentReconciles == 0 for each controller. The operator is waiting for a ProjectClaim custom resource instance of an object to be created. Until that happens, there will be no further logs, everything is quiet.

Solution

This is expected behavior. Please type:

$ kubectl create -f deploy/crds/gcp.managed.openshift.io_v1alpha1_projectclaim_cr.yaml