Troubleshooting
Problem
You will find these errors in the VM where API Connect upgrade is failing after ssh to it and running the following command :
journalctl -u appliance-manager -f
<date> <host> kubelet[547853]: E0720 10:14:06.993195 547853 remote_runtime.go:198] "RunPodSandbox from runtime service failed" err="rpc error: code = Unknown desc = failed to get sandbox image \"registry.k8s.io/pause:3.6\": failed to pull image \"registry.k8s.io/pause:3.6\": failed to pull and unpack image \"registry.k8s.io/pause:3.6\": failed to resolve reference \"registry.k8s.io/pause:3.6\": failed to do request: Head \"https://registry.k8s.io/v2/pause/manifests/3.6\": read tcp <ip>:<port>-><ip>:<port>: read: connection reset by peer"
Cause
This is because the default sandbox image in the latest version of containerd uses registry.k8s.io/pause:3.6 but in prior releases we used pause images at a different path k8s.gcr.io/pause:3.x.
Resolving The Problem
This is fixed in the latest control plane files where the missing image (registry.k8s.io/pause:3.6) was included and uploaded to fix central on the 11th May 2023. If you need a workaround execute:
cd /usr/local/lib/appliance-control-plane/1.25.0/ && gunzip kubernetes.tgz && ctr -n k8s.io images import kubernetes.tar
Document Location
Worldwide
[{"Type":"MASTER","Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSMNED","label":"IBM API Connect"},"ARM Category":[{"code":"a8m50000000CeCAAA0","label":"API Connect-\u003EManagement and Monitoring (MM)-\u003EUpgrade\/Downgrade"}],"ARM Case Number":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"10.0.1;10.0.5"}]
Was this topic helpful?
Document Information
Modified date:
20 July 2023
UID
ibm17013525