Introduction
When changing the IP address of a Terraform Enterprise instance server, you must also update the IP address within the underlying Replicated configuration. This ensures the Terraform Enterprise application remains operable after the network change.
Use Case
This procedure is necessary when migrating a Terraform Enterprise instance to a new Virtual Private Cloud (VPC) or any other scenario that results in a change to the server's primary IP address. Failing to update the Replicated configuration after an IP change can prevent Terraform Enterprise services from starting correctly.
Procedure
This workflow involves modifying the PRIVATE_ADDRESS, DAEMON_HOST, and PUBLIC_ADDRESS parameters in the Replicated operator configuration files and restarting the associated services.
Note: On systemd-based systems such as RHEL, CentOS, and modern Ubuntu versions, these configuration files are typically located at
/etc/sysconfig/replicatedand/etc/sysconfig/replicated-operator. You may also find them in the/etc/defaultdirectory.
- Connect to the Terraform Enterprise instance server using SSH.
- Edit the
/etc/sysconfig/replicatedfile and update thePRIVATE_ADDRESSparameter with the new IP address. - Edit the
/etc/sysconfig/replicated-operatorfile and update thePRIVATE_ADDRESS,DAEMON_HOST, andPUBLIC_ADDRESSparameters with the new IP address. -
Verify that the Docker service is running.
# systemctl status docker
If the service is not active, start it.
# systemctl start docker
-
Restart the Replicated services to apply the IP address changes.
# systemctl restart replicated replicated-operator
Verification
-
Check the status of the Replicated services to ensure they started successfully.
# systemctl status replicated # systemctl status replicated-operator
- Attempt to access the Terraform Enterprise web UI using the new IP address or associated DNS name to confirm the application is operational.
Additional Information
For more details from the vendor, please see Replicated's documentation on How to Handle an IP Change.