Closed lyudmilalala closed 2 years ago
This seems the same issue with https://github.com/apache/openwhisk/issues/5260 and it is supposed to be handled by https://github.com/apache/openwhisk-deploy-kube/pull/730
@hugy718 Is your issue resolved with the change?
The reason here is that @lyudmilalala is using the OpenWhisk Helm repo which points to the release version 1.0.0 from 2021.
This version does not include the fix and I can confirm that deploying version 1.0.0 through the Helm repo yields the problem that @lyudmilalala is describing.
When using the latest commit (3c8a72e73f724ae941bc33a8ad72797b21725088), this problem does not exist anymore.
Maybe it is a wise decision to publish another version in the Helm repo that works.
This seems the same issue with apache/openwhisk#5260 and it is supposed to be handled by #730
@hugy718 Is your issue resolved with the change?
Yes, the same issue. Should be fixed by the latest commit. @lyudmilalala May you try to deploy the latest commit. The steps are the same, and additional configurations needed.
Close this as many people have confirmed that it is caused by the image version.
Need to publish a new version to the helm repo. I am not sure if we have permission to do this.
If the update of helm repo cannot be done for a while, I would be glad to submit a push request to add warning in the deployment guidance to warn people about this thing.
@lyudmilalala The change is already included in the master. Please try again with the latest master.
Possibly related to https://github.com/npm/cli/issues/5032.
The reason here is that @lyudmilalala is using the OpenWhisk Helm repo which points to the release version 1.0.0 from 2021. This version does not include the fix and I can confirm that deploying version 1.0.0 through the Helm repo yields the problem that @lyudmilalala is describing.
When using the latest commit (3c8a72e), this problem does not exist anymore.
Maybe it is a wise decision to publish another version in the Helm repo that works.
Hii @linuswagner I was able to get same error as mentioned earlier. I was unable to resolve the error. Can you specify the commands or changes we need to perform.
I am trying to deploy Openwhisk on Windows Docker Desktop k8s
If I following the Deploying Released Charts from Helm Repository Section in README, the install-package pod will finally get status
Error
.Final status of pods looks like this
Part of the install-package log shows as below, and the full log is here.
Steps to reproduce the problem
Environment Windows 10 64bit docker desktop version 4.3.0 docker version 20.10 k8s version 1.22.4 helm version 3.4.2
mycluster.yaml
Follow the instructions in README, run
My guess
I think it is because npm v3.5.2 has been outdated for a long time.
I also notice that some docker images used by Deploying Released Charts from Helm Repository is much older than those used by Deploying from Git, for example the
openwhisk/ow-utils
image. I don't know if it is related to that this problem only occurs when I deploy by charts from the helm repository. (I cannot find npm version in logs when deploying from git. I am not really sure which docker container correspond to the install-package pod, so I also cannot enter it and see its npm version.)Helm repo of Openwhisk is here. On the right hand side you can see Containers images.
I also want to know what potential differences will these different versions of images bring to my cluster.
Also, by the way, the service only generate at most four install-package pods. To make debug easier, I want to know if there is a way to let the deploy generate a new install-package pod automatically after the old ones are deleted.