Problem
A new module version is failing to upload. When checking the Get a Module API the status shows reg_ingressing and never progresses to setup_complete.
Prerequisites
- Terraform Enterprise versions prior to
v202308-1
Cause
An invalid or malformed file may be present in the module directory.
-
In the example below, a symlink was incorrectly set with the contents of the
variables.tffile.
❯ examples/test-module ls -lah
lrwxrwxrwx variables.tf ⇒ variable "region_primary" {
type = string
description = "AWS primary region to deploy to"
}
- In Terraform Enterprise versions prior to
v202308-1, Terraform Enterprise did not check for certain types of corrupt files such as the above example that could not be uploaded, causing publishing to fail.
Solution:
-
Review the contents of your module files. Check to ensure they are valid, do not contain incorrect symlinks, and are not malformed or corrupt.
-
Once any invalid files are corrected, delete the module version using the Delete a Module API.
-
If using VCS, ensure that the tagged version is either deleted or incremented to a new version number.
-
-
Ensure that the invalid file is not included in any tagged version of the module as that could cause the entire module to fail to upload.
-
If just the one tagged version was failing to upload, a new tagged version should trigger the module to ingress the new version.
-
However if the whole module is failing to upload and not just a single version, Delete the entire module and upload it again after confirming that the invalid file was corrected.
-
Outcome
Once any invalid files are removed or corrected, the new module or module versions should upload and ingress to the Private Module Registry in Terraform Enterprise as expected.
Additional Information
-
If issues persist, please reach out to HashiCorp Support for assistance.