The error “context deadline exceeded” implies that we ran into a situation where a given action was not finished in an anticipated timeframe.<\/p>\n
Generally, the issue occurs when Pods are stuck in Init status.<\/p>\n
The normal error looks as shown below:<\/p>\n
Warning FailedCreatePodSandBox 93s (x8 over 29m) kubelet, 97011e0a-f47c-4673-ace7-d6f74cde9934 Failed to create pod sandbox: rpc error: code = DeadlineExceeded desc = context deadline exceeded Normal SandboxChanged 92s (x8 over 29m) kubelet, 97011e0a-f47c-4673-ace7-d6f74cde9934 Pod sandbox changed, it will be killed and re-created.<\/p>\n
You can also check the status of the node-agent-hyperbus by running the following nsxcli command from the node (as root user):<\/p>\n
\r\nsudo -i\r\n\/var\/vcap\/jobs\/nsx-node-agent\/bin\/nsxcli\r\n\u201cat the nsx-cli prompt, enter\u201d: get node-agent-hyperbus status<\/pre>\nAnticipated output:<\/p>\n
HyperBus status: Healthy<\/pre>\nIn this situation you would see the following error instead:<\/p>\n
% An internal error occurred<\/p>\n
This causes a loop of DEL (delete) requests to the nsx-node-agent process<\/p>\n
Restarting the nsx-node-agent process will resolve this error:<\/p>\n
Use the \u201cbosh ssh\u201d command to access the worker node<\/p>\n
Then, run the following commands.<\/p>\n
sudo -i\r\nmonit restart nsx-node-agent<\/pre>\nSit tight and wait for nsx-node-agent to restart: watch monit summary<\/p>\n
This should resolve the issue.<\/p>\n","protected":false},"excerpt":{"rendered":"
The error “context deadline exceeded” implies that we ran into a situation where a given action was not finished in an anticipated timeframe. Generally, the issue occurs when Pods are stuck in Init status. The normal error looks as shown below: Warning FailedCreatePodSandBox 93s (x8 over 29m) kubelet, 97011e0a-f47c-4673-ace7-d6f74cde9934 Failed to create pod sandbox: rpc […]<\/p>\n