We run into this when e.g. specifying a non-existing image in containerTemplate.
The pod will be stuck in Waiting: ImagePullBackOff (without the build log showing that problem).
The build will be waiting at
(code at tag 0.11).
If the user tries to abort the build (which they will), the ONLY option that works is "forcibly abort the whole build". This has the downside that
- the pod will not be deleted in kubernetes
- the podTemplate will stay around in the global Jenkins configuration ($JENKINS_URL/configure)