Closed tanjunchen closed 3 years ago
for this error
Error adding/updating listener(s) virtualInbound: Invalid path: /var/local/lib/wasme-cache/0295d929353976266ab721389ec859b2fe012d63ce2e58815469ab85c123b510
i found that 0295d929353976266ab721389ec859b2fe012d63ce2e58815469ab85c123b510 is not found in /var/local/lib/wasme-cache. You can exec wasme deploy and then wasme undeploy, which should reproduce the problem. Or change a file and recompile, you will find that the image has changed, but the files in the /var/local/lib/wasme-cache directory seem to have not changed. It may be related to configmap、daemon in wasme.
INFO[0000] cache namespace already exists cache=wasme-cache.wasme image="quay.io/solo-io/wasme:0.0.33"
INFO[0000] cache configmap already exists cache=wasme-cache.wasme image="quay.io/solo-io/wasme:0.0.33"
INFO[0000] cache service account already exists cache=wasme-cache.wasme image="quay.io/solo-io/wasme:0.0.33"
INFO[0000] cache role updated cache=wasme-cache.wasme image="quay.io/solo-io/wasme:0.0.33"
INFO[0000] cache rolebinding updated cache=wasme-cache.wasme image="quay.io/solo-io/wasme:0.0.33"
INFO[0000] cache daemonset updated cache=wasme-cache.wasme image="quay.io/solo-io/wasme:0.0.33"
INFO[0007] image is already cached cache="{wasme-cache wasme}" image="webassemblyhub.io/tanjunchen20/add-header:v0.1"
i guess there is a bug in following process.
it can be resolved by delete the po in wasme namespace. laughing
we need to check the SHA of image not the image name. see https://github.com/solo-io/wasm/blob/master/tools/wasme/cli/pkg/deploy/istio/istio_provider.go#L234
Describe the bug A clear and concise description of what the bug is.
I was using the latest version of wasm, deployed istio 1.9.1, and found that istio-proxy failed.
the logs of the productpage-v1-c9b48dd87-mtqgv/istio-proxy
the logs of istiod
the envoyfliter of productpage-v1-myfilter
To Reproduce Steps to reproduce the behavior:
Expected behavior A clear and concise description of what you expected to happen.
We can use the wasme function correctly according to https://docs.solo.io/web-assembly-hub/latest/tutorial_code/deploy_tutorials/deploying_with_istio/
Additional context Add any other context about the problem here, e.g.
istio 1.9.1