Comment 5 for bug 1917308

It is possible that the 5 second timeout on the tiller command is not long enough based on the current responsiveness of the system

2021-03-01T11:36:32.683 controller-0 containerd[78918]: info time="2021-03-01T11:36:32.683511061Z" level=info msg="Exec for \"a00cf66fa21b19f28771a99a2aa85643c1fbfd2ed9d19d0f10c2a8ac7925cc1b\" with command [/bin/sh -c PATH=/bin:/usr/bin:/usr/local/bin:/tmp HELM_HOST=:24134 /bin/sh -c 'helm list --namespace openstack --pending --tiller-connection-timeout 5'], tty false and stdin false"
2021-03-01T11:36:32.683 controller-0 containerd[78918]: info time="2021-03-01T11:36:32.683554708Z" level=info msg="Exec for \"a00cf66fa21b19f28771a99a2aa85643c1fbfd2ed9d19d0f10c2a8ac7925cc1b\" returns URL \"http://127.0.0.1:45461/exec/efyQ6dTd\""

and that the command is being prematurely terminated before it could complete.