Jun 8 10:19:57.162893 r-bulldog-03 INFO kubelet[23191]: E0608 10:19:57.161271 23191 kuberuntime_sandbox.go:41] GeneratePodSandboxConfig for pod "snmp-sv2-zv6mw_default(20d56030-58f3-4cb1-8b50-ccd4dd2c91e4
)" failed: open /run/systemd/resolve/resolv.conf: no such file or directory
Jun 8 10:19:57.163095 r-bulldog-03 INFO kubelet[23191]: E0608 10:19:57.161345 23191 kuberuntime_manager.go:727] createPodSandbox for pod "snmp-sv2-zv6mw_default(20d56030-58f3-4cb1-8b50-ccd4dd2c91e4)" failed: open /run/systemd/resolve/resolv.conf: no such file or directory
Jun 8 10:19:57.163334 r-bulldog-03 INFO kubelet[23191]: E0608 10:19:57.161466 23191 pod_workers.go:191] Error syncing pod 20d56030-58f3-4cb1-8b50-ccd4dd2c91e4 ("snmp-sv2-zv6mw_default(20d56030-58f3-4cb1-8
b50-ccd4dd2c91e4)"), skipping: failed to "CreatePodSandbox" for "snmp-sv2-zv6mw_default(20d56030-58f3-4cb1-8b50-ccd4dd2c91e4)" with CreatePodSandboxError: "GeneratePodSandboxConfig for pod \"snmp-sv2-zv6mw_d
efault(20d56030-58f3-4cb1-8b50-ccd4dd2c91e4)\" failed: open /run/systemd/resolve/resolv.conf: no such file or directory"
Describe the results you expected:
Container is deployed successfully. Local container is stopped, kube managed container is starting.
Description
Container does not start due to "failed: open /run/systemd/resolve/resolv.conf: no such file or directory"
Steps to reproduce the issue:
config kubernetes server ip <VIP>
Describe the results you received:
Describe the results you expected:
Container is deployed successfully. Local container is stopped, kube managed container is starting.
Output of
show version
:Output of
show techsupport
:Additional information you deem important (e.g. issue happens only occasionally):
There is a W/A:
sonic_dump_r-bulldog-03_20210608_102022.tar.gz