Error creating network add on pod

[DirectedSoul1]

Steps followed and environment used

Openshift

Using Openshift 3.11

[root@shedge-master0 hyperconverged-cluster-operator]# oc version
oc v3.11.104
kubernetes v1.11.0+d4cacc0
features: Basic-Auth GSSAPI Kerberos SPNEGO

Server https://shedge-master0.cnv-comm.10.8.120.140.nip.io:8443
openshift v3.11.104
kubernetes v1.11.0+d4cacc0

After deploying all the CRD's and CR for HCO , network add-on pod fails

[root@shedge-master0 hyperconverged-cluster-operator]# oc get all
NAME                                                   READY     STATUS             RESTARTS   AGE
pod/cdi-apiserver-64d8d44d4-cj7wq                      1/1       Running            0          1h
pod/cdi-deployment-6b997bddf6-lhm68                    1/1       Running            0          1h
pod/cdi-operator-65767d954d-v9tlk                      1/1       Running            0          1h
pod/cdi-uploadproxy-848f576f98-s4mjz                   1/1       Running            0          1h
pod/cluster-network-addons-operator-5f4d4854bd-k2b75   0/1       CrashLoopBackOff   20         1h
pod/hyperconverged-cluster-operator-6b7ccc5df8-wzzdx   1/1       Running            0          1h
pod/kubevirt-hyperconverged-cluster-jobfkgxl-xb9l5     0/1       ImagePullBackOff   0          1h
pod/virt-operator-86b75548c-gdcht                      1/1       Running            0          1h

NAME                      TYPE        CLUSTER-IP       EXTERNAL-IP   PORT(S)   AGE
service/cdi-api           ClusterIP   172.30.52.160    <none>        443/TCP   1h
service/cdi-uploadproxy   ClusterIP   172.30.188.198   <none>        443/TCP   1h

NAME                                              DESIRED   CURRENT   UP-TO-DATE   AVAILABLE   AGE
deployment.apps/cdi-apiserver                     1         1         1            1           1h
deployment.apps/cdi-deployment                    1         1         1            1           1h
deployment.apps/cdi-operator                      1         1         1            1           1h
deployment.apps/cdi-uploadproxy                   1         1         1            1           1h
deployment.apps/cluster-network-addons-operator   1         1         1            0           1h
deployment.apps/hyperconverged-cluster-operator   1         1         1            1           1h
deployment.apps/virt-operator                     1         1         1            1           1h

NAME                                                         DESIRED   CURRENT   READY     AGE
replicaset.apps/cdi-apiserver-64d8d44d4                      1         1         1         1h
replicaset.apps/cdi-deployment-6b997bddf6                    1         1         1         1h
replicaset.apps/cdi-operator-65767d954d                      1         1         1         1h
replicaset.apps/cdi-uploadproxy-848f576f98                   1         1         1         1h
replicaset.apps/cluster-network-addons-operator-5f4d4854bd   1         1         0         1h
replicaset.apps/hyperconverged-cluster-operator-6b7ccc5df8   1         1         1         1h
replicaset.apps/virt-operator-86b75548c                      1         1         1         1h

NAME                                                 DESIRED   SUCCESSFUL   AGE
job.batch/kubevirt-hyperconverged-cluster-jobfkgxl   1         0            1h

Logs for the pod( network addon is below):

[root@shedge-master0 hyperconverged-cluster-operator]# oc logs pod/cluster-network-addons-operator-5f4d4854bd-k2b75
2019/04/12 16:10:27 Go Version: go1.10.8
2019/04/12 16:10:27 Go OS/Arch: linux/amd64
2019/04/12 16:10:27 version of operator-sdk: v0.5.0+git
2019/04/12 16:10:27 registering Components
2019/04/12 16:10:27 failed setting up operator controllers: environment variable OPERATOR_NAMESPACE has to be set

There was no mention of the variable OPERATOR_NAMESPACE anywhere in the README.md

[phoracek]

Thanks for reporting this, I believe it will be fixed with #25

[rthallisey]

Looks like this error is still showing: https://github.com/kubevirt/cluster-network-addons-operator/blob/master/pkg/controller/networkaddonsconfig/networkaddonsconfig_controller.go#L55

@DirectedSoul1 I just published a new HCO image. See if that helps.

[tripledes]

@rthallisey I just checked out the sources and followed the instructions on the README, still hitting this issue, the only workaround is to actually set the environment variable on the deployment cluster-network-addons-operator, with its value set to kubevirt-hyperconverged, that makes the operator to run.

[phoracek]

Will look into that.

[DirectedSoul1]

I just tested the latest HCO image in my minikube environment and even after setting the OPERATOR_NAMESPACE=kubevirt-hyperconverged , Im not able to see the network-addon pod in working state. ``` /minikube/apr_16/hyperconverged-cluster-operator root@shegde🎩kubectl logs pod/cluster-network-addons-operator-7ff5c6b47c-w2frd 2019/04/16 14:32:47 Go Version: go1.10.8 2019/04/16 14:32:47 Go OS/Arch: linux/amd64 2019/04/16 14:32:47 version of operator-sdk: v0.5.0+git 2019/04/16 14:32:47 registering Components 2019/04/16 14:32:47 failed setting up operator controllers: environment variable OPERATOR_NAMESPACE has to be set ``` ``` ~/minikube/apr_16/hyperconverged-cluster-operator root@shegde🎩kubectl get all --namespace=kubevirt-hyperconverged NAME READY STATUS RESTARTS AGE pod/cdi-apiserver-769fcc7bdf-b67rn 1/1 Running 0 5m4s pod/cdi-deployment-8b64c5585-gz46d 1/1 Running 0 5m4s pod/cdi-operator-c77447cc7-pzgrq 1/1 Running 0 8m43s pod/cdi-uploadproxy-8dcdcbff-q4fr6 1/1 Running 0 5m4s pod/cluster-network-addons-operator-7ff5c6b47c-w2frd 0/1 CrashLoopBackOff 6 8m43s ``` * Shashank Hegde* Systems Engineer, RHCE * Westford, US* *cell*: 6179925192, *email*: shegde@redhat.com

…

On Mon, Apr 15, 2019 at 8:43 PM Ryan Hallisey ***@***.***> wrote: Looks like this error is still showing: https://github.com/kubevirt/cluster-network-addons-operator/blob/master/pkg/controller/networkaddonsconfig/networkaddonsconfig_controller.go#L55 @DirectedSoul1 <https://github.com/DirectedSoul1> I just published a new HCO image. See if that helps. — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub <#27 (comment)>, or mute the thread <https://github.com/notifications/unsubscribe-auth/AnLnAU8dm83nsTu208u-zR1bxGZxtj62ks5vhRzLgaJpZM4csd8J> .

[phoracek]

Maybe #32 and #29 will help