Because the UI creates a template version, then a template. Creating this template hangs forever. We should at the very least add a message to tell the user what is going on.

This issue does not try to resolve the issue of orphaned versions.

There should be some method of the polling action to determine if the job is in a queue, and if that queue is stuck. This could be because no provisioners exist, or the tag combination does not exist. In these cases, we should tell the user this will never advance.

This probably requires some backend work to determine the "broken" state.