-
Hello, Below are the commands I executed:
But when I execute the following:
The ' meep-virt-engine-54f8b885b5-6jbnm ' seems to be not running. And there are also issues with 'meep-ingress-controller-cnpxj' whose status is shown as "CrashLoopBackOff". Would these issues create problems while doing the basic operations (e.g., deploy Demo1) (https://github.com/InterDigitalInc/AdvantEDGE/wiki/basic-operation)? Thanks a lot in advance! |
Beta Was this translation helpful? Give feedback.
Replies: 2 comments 8 replies
-
Hello @Deu82 , Thanks for reaching out. I would need some more info to help diagnose the problem. 1- versions of what is currently running: Note that mangling at the end of pod names may be different if you tried to restart... This will help to figure what is going on. |
Beta Was this translation helpful? Give feedback.
-
This is exactly the same problem I am facing in the ingress controller. I have removed the
Fair warning: My application is still not up as I seem to have an unrelated error somewhere else. |
Beta Was this translation helpful? Give feedback.
Hello @Deu82 ,
Thanks for reaching out.
Ingress controller and Virt engine are necessary to the platform operation.
I would need some more info to help diagnose the problem.
1- versions of what is currently running:
meepctl version all
2- commit that you are running using, from the AdvantEDGE clone folder:
git log --oneline --decorate --graph
3- description of failing pods:
kubectl describe pods meep-virt-engine-54f8b885b5-6jbnm
andkubectl describe pods meep-ingress-controller-cnpxj
4- logs of failing pods:
kubectl log meep-virt-engine-54f8b885b5-6jbnm
andkubectl log meep-ingress-controller-cnpxj
Note that mangling at the end of pod names may be different if you tried to restart...
This…