topic Re: cn series pan-ngfw pod not ready in CN-Series Discussions

cn series pan-ngfw pod not ready

skchakraborty — Sun, 14 Jan 2024 18:45:56 GMT

Hi All,

While working for CN series deployment, pan-ngfw pods are not becoming ready status , as getting this error in logs

Readiness probe failed: Panorama config is not pushed. pan_task is not running.

However, eks cluster monitoring status can show kube-system pod from panorama.

Can anyone guide for more debugging information.

Thanks in advance..

Re: cn series pan-ngfw pod not ready

Luongchacha1 — Thu, 21 Mar 2024 05:46:33 GMT

Hello skchakraborty,

Is there any update on this problem?. Have you fix this?

Re: cn series pan-ngfw pod not ready

skchakraborty — Fri, 22 Mar 2024 07:17:30 GMT

@Luongchacha1 , due to time constaints I've to stop the project, but soon I will start the project agian. Are you also doing similar deployment or you have already done the deployment

Re: cn series pan-ngfw pod not ready

Luongchacha1 — Sat, 23 Mar 2024 05:01:11 GMT

Yes, i am, i catch similar error like ya.

Re: cn series pan-ngfw pod not ready

DNguyen46 — Mon, 22 Apr 2024 10:13:34 GMT

Hi, have you been able to fix that error? I'm having the same thing too

Re: cn series pan-ngfw pod not ready

YLesev — Thu, 23 May 2024 15:03:43 GMT

The readiness probe for the ngfw pods, expects "trigger" from the pan-cni pods. (literally a specific directory to be created).
I'd start checking if everything with the pan-cni is good - they have to succeed "to inject" cni config to the nodes. For example (for a on-prem native kubernetes cluster) pan-cni populate the node (host) with some binaries, make some changes on the node (host) cni config files .. and then "marked" the success by creating a directory, which the ngfw pods "picks" as trigger to continue with the startup process (and the ngfw pods to become fully running)