From 853b99576b4bc325a0c927726385f9d6324984a8 Mon Sep 17 00:00:00 2001 From: Kalya Subramanian <42158129+ksubrmnn@users.noreply.github.com> Date: Tue, 26 Jan 2021 11:28:43 -0800 Subject: [PATCH] docs(upgrade): Add upgrade troubleshooting guide (#2377) Signed-off-by: Kalya Subramanian --- docs/troubleshooting/upgrade.md | 17 +++++++++++++++++ 1 file changed, 17 insertions(+) create mode 100644 docs/troubleshooting/upgrade.md diff --git a/docs/troubleshooting/upgrade.md b/docs/troubleshooting/upgrade.md new file mode 100644 index 0000000000..b867d29e04 --- /dev/null +++ b/docs/troubleshooting/upgrade.md @@ -0,0 +1,17 @@ +# OSM Upgrade Troubleshooting Guide + +## Server could not find requested resource +If the [upgrade CRD guide](../upgrade_guide.md##crd-upgrades) was not followed, it is possible that the installed CRDs are out of sync with the OSM controller. + +The OSM controller will then crash with errors similar to this: +``` +reflector.go:178] pkg/mod/k8s.io/client-go@v0.18.6/tools/cache/reflector.go:125: Failed to list *v1alpha2.TrafficTarget: the server could not find the requested resource (get traffictargets.access.smi-spec.io) +``` +To resolve these errors: +1. Checkout the correct release branch of the [repo](https://github.com/openservicemesh/osm) and run the following commands from the root. +1. Delete existing CRDs and Custom Resources (TrafficTargets, TrafficSplits, etc.) + - `./scripts/cleanup/crd-cleanup.sh` +1. Install the new CRDs + - `kubectl apply -f charts/osm/crds/` +1. Restart the osm-controller pod +1. Recreate CustomResources