Network Reliability Engineering Community

Lesson timeout when booting the vQFX

We were trying to load lessons locally but when it tries to spin up the vQFX it

doesn’t work. One of the lessons we tried to load was the ‘Network Unit Testing with

JSNAPY’ lesson. I checked the logs for the nginx

controller kubectl pod and on syringe docker container. Also, I investigated the docker container for vQFX logs, I found some errors there too.

Do you have any ideas on what I can do to make it work looking at the logs?

Logs on kubectl nginx controller pod

W0518 10:14:07.537193       1 backend_ssl.go:54] error obtaining PEM from secret default/: secret named default/ does not exist
W0518 10:14:07.537342       1 backend_ssl.go:54] error obtaining PEM from secret 13-9lr1dx1vg39wl7op-ns/tls-certificate: secret named 13-9lr1dx1vg39wl7op-ns/tls-certificate does not exist
W0518 10:14:17.537942       1 backend_ssl.go:54] error obtaining PEM from secret default/: secret named default/ does not exist
W0518 10:14:17.538282       1 backend_ssl.go:54] error obtaining PEM from secret 13-9lr1dx1vg39wl7op-ns/tls-certificate: secret named 13-9lr1dx1vg39wl7op-ns/tls-certificate does not exist
W0518 10:14:27.539432       1 backend_ssl.go:54] error obtaining PEM from secret 13-9lr1dx1vg39wl7op-ns/tls-certificate: secret named 13-9lr1dx1vg39wl7op-ns/tls-certificate does not exist
W0518 10:14:27.539468       1 backend_ssl.go:54] error obtaining PEM from secret default/: secret named default/ does not exist
W0518 10:14:37.542575       1 backend_ssl.go:54] error obtaining PEM from secret default/: secret named default/ does not exist
W0518 10:14:37.542642       1 backend_ssl.go:54] error obtaining PEM from secret 13-9lr1dx1vg39wl7op-ns/tls-certificate: secret named 13-9lr1dx1vg39wl7op-ns/tls-certificate does not exist
W0518 10:14:47.547025       1 backend_ssl.go:54] error obtaining PEM from secret 13-9lr1dx1vg39wl7op-ns/tls-certificate: secret named 13-9lr1dx1vg39wl7op-ns/tls-certificate does not exist
W0518 10:14:47.547083       1 backend_ssl.go:54] error obtaining PEM from secret default/: secret named default/ does not exist

``
Logs on syringe docker container

  time="2019-05-29T09:38:01Z" level=info msg="Job Status" active=1 failed=5 jobName=config-vqfx1 successful=0
time="2019-05-29T09:38:01Z" level=error msg="Problem configuring with config-vqfx1"
10.32.0.5 - - [29/May/2019:09:38:02 +0000] "GET /exp/livelesson/12-9lr1dx1vg39wl7op HTTP/1.1" 200 3051
time="2019-05-29T09:38:02Z" level=info msg="Job Status" active=1 failed=4 jobName=config-vqfx3 successful=0
time="2019-05-29T09:38:02Z" level=error msg="Problem configuring with config-vqfx3"
time="2019-05-29T09:38:02Z" level=info msg="Job Status" active=1 failed=4 jobName=config-vqfx2 successful=0
time="2019-05-29T09:38:02Z" level=error msg="Problem configuring with config-vqfx2" 

Logs on vQFX container using docker inspect

$ docker logs ddbb72ea3140
Device "net1" does not exist.
Cannot find device "net1"
Device "net2" does not exist.
Cannot find device "net2"
Device "net3" does not exist.
Cannot find device "net3"
Device "net4" does not exist.
Cannot find device "net4"
Device "net5" does not exist.
Cannot find device "net5"
Device "net6" does not exist.
Cannot find device "net6"
Device "net7" does not exist.
Cannot find device "net7"
Device "net8" does not exist.
Cannot find device "net8"
Device "net9" does not exist.
Cannot find device "net9"
Device "net10" does not exist.
Cannot find device "net10"

Can you provide us some more details? I’d like to replicate this so I can troubleshoot it.

  1. What OS are you using?
  2. What version of minikube?
  1. Ubuntu 18.04.2
  2. Minikube v.0.34.1

Thanks!

I am not able to replicate this. I’ve deleted existing clones of both nrelabs-curriculum and antidote-selfmedicate, and re-cloned from master.

How much RAM, storage, etc?

We might have to do a conference call so you can show me what you’re running into. What time might you have available to do this?

These errors are from a while ago now.

I pulled from git and setup again but there is still the same problem.

A call would be really useful, I will send you a message on slack to arrange a time.

Thank you