[GitHub] [openwhisk-deploy-kube] s117 commented on issue #673: Cannot deploy on kind because of couchdb-init failure

[GitBox <gi...@apache.org>]

s117 commented on issue #673:
URL: https://github.com/apache/openwhisk-deploy-kube/issues/673#issuecomment-869067074


   > Thanks again for checking. I followed your suggestion and tried executing the command on which Ansible fails (`/bin/findmnt --list --noheadings --notruncate`) on the container via `kubectl exec`. And it works without issues...
   > However, the pod eventually enters the Failed state with the same output.
   > 
   > At this point, I am even more confused about the problem. It is probably related to my own environment (maybe Docker version? I am using Docker 20.10.3 on Linux). I will verify if the same thing happens on a different Linux machine, as soon as I have some time to do so.
   > Anyway, although annoying, the issue is not blocking for me as I managed to deploy OpenWhisk on Minikube.
   
   I just came across the same problem. It turns the timeout is caused by Python rather than `/bin/findmnt`. Below are some related upstream tickets:
   https://github.com/ansible/ansible/issues/24228#issuecomment-409693926
   https://bugs.python.org/issue1663329
   https://bugs.python.org/issue11284
   
   My system runs Arch Linux also, and inside the container `ulimit -n` returns a large value. My workaround is to modify `helm/openwhisk/configMapFiles/initCouchDB/initdb.sh` to apply [this patch](https://github.com/ansible/ansible/commit/23371b5617cb02ae0edfc46ee6fc4ee8f5f0a523) to `/usr/local/lib/python2.7/dist-packages/ansible/plugins/shell/__init__.py` before using ansible.
   
   
   


-- 
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

To unsubscribe, e-mail: issues-unsubscribe@openwhisk.apache.org

For queries about this service, please contact Infrastructure at:
users@infra.apache.org