<p>We have a simple release test for a <code>Redis</code> chart. After running <code>helm test myReleaseName --tls --cleanup</code>, we got </p>

<pre><code>RUNNING: myReleaseName-redis
ERROR: timed out waiting for the condition
</code></pre>

<p>There are several issues in Github repository at <a href="https://github.com/helm/helm/search?q=timed+out+waiting+for+the+condition&amp;type=Issues" rel="noreferrer">https://github.com/helm/helm/search?q=timed+out+waiting+for+the+condition&amp;type=Issues</a> but I did not find a solution to it. </p>

<p>What's going on here?</p>

<p>This first looks puzzling and shows little information because <code>--cleanup</code> will kill the pods after running. One can remove it to get more information. I, thus, reran the test with </p>

<pre><code>helm test myReleaseName --tls --debug
</code></pre>

<p>Then use <code>kubectl get pods</code> to examine the pod used for testing. (It could be of other names.) </p>

<pre><code>NAME                                                 READY     STATUS             RESTARTS   AG
myReleaseName-redis                                            0/1       ImagePullBackOff   0          12h
</code></pre>

<p>From here, it is more clear now that there is something wrong with images, and it turned out that <strong>the link used to pull the image is not correct</strong>. (Use <code>kubectl describe pod &lt;pod-name&gt;</code> and then you can find the link you used to pull the image.)</p>

<p>Fix the link, and it worked.</p>
