Problem
An abnormally long wait period can be experienced during a run, between when the plan output completed and the next phase or action occurs, such as having the Confirm&Apply option become available to continue, or the Cost Estimation/Sentinel/Apply phase of the run workflow initiating.
Cause
This can be caused by one of these reasons, or a combination of both:
- The Terraform binary version configured for the workspace is less than
v0.15.5- There was back-end logic optimizations made in this version to optimize the performance of this part of the workflow
- The storage driver configured for Docker is not
overlay2- Per Docker's documentation,
overlay2is the preferred storage driver for all currently supported Linux distributions
- Per Docker's documentation,
Solutions:
-
Upgrading the Terraform binary version being utilized by your workspace to at least
v0.15.5- You can select
v0.15.5within the drop-down box for the Terraform Version field found within Settings > General in the workspace- If you do not see
v0.15.5as an option, you may have an older version of TFE that did not have that version included so you will need to manually add that version to the list of available versions for your TFE installation by following this article's instructions -
If your workspace has been using a version less than
v0.15.0, please review and apply what's found in the upgrade guide before configuring the new version. This is to ensure that your configuration code will be compatible with changes between the version you have configured and thev0.15major version
- If you do not see
- You can select
-
Upgrading the storage driver configured for Docker to
overlay2- Confirm what storage driver Docker is currently using by running
docker infoand looking for theStorage Driverline. If it's notoverlay2, please refer to Docker's documentation for steps on how to change the configured storage driver.- Keep in mind that changing the storage driver makes existing containers and images inaccessible on the local system.
- You will want to stop the Terraform Enterprise application prior to this modification.
- Use
docker saveto save any custom images you have built or push them to Docker Hub or a private registry before changing the storage driver, so that you do not need to re-create them later.
- Keep in mind that changing the storage driver makes existing containers and images inaccessible on the local system.
- Confirm what storage driver Docker is currently using by running
Outcome
You should see a decrease in the amount of wait time between actions after a run's plan is completed. If not please reach out to support@hashicorp.com, and inform within your request that you have performed the steps within this ticket.