Set a custom maximum number of Terraform jobs to process in parallel per cam-provider-terraform pod:
-
Run the following command to edit the deployment for cam-provider-terraform:
kubectl -n management-infrastructure-management edit deployment cam-provider-terraform -
Update the value of MAX_LOCAL_TERRAFORM_JOBS.
containers: - env: - name: MAX_LOCAL_TERRAFORM_JOBS value: "10"In this example, it is set to 10.
.Managed services on IBM Cloud Pak® for Multicloud Management has a predefined 6 hours deployment window. Do the following steps to add TERRAFORM_JOB_TIMEOUT_MS environment variable to the deployment:
-
Run the following command to open the deployment in edit mode:
kubectl -n management-infrastructure-management edit deployment cam-provider-terraform -
Add the
TERRAFORM_JOB_TIMEOUT_MSvariable with value.For example, the value of
TERRAFORM_JOB_TIMEOUT_MSis updated to 10 hours in millisecond:name:TERRAFORM_JOB_TIMEOUT_MS value: "36000000"
During template deployment, you must specify user credentials based on the operating system.
- For IBM Cloud with Red Hat Enterprise Edition operating system, specify "root" as the user.
- For AWS with Red Hat Enterprise Edition operating system, specify "ec2-user" as the user.
- For AWS with Ubuntu operating system, specify "ubuntu" as the user name.
If the appropriate user is not provided for the corresponding operating system, then the deployment fails with an error message.
For example, If you do not provide "root" as the user while deploying a VMware template and the passwordless sudo is also not enabled, then the following error message is displayed:
Error: Response from pattern manager:
StatusCode:500
Message:
{
“message”: “Bootstrap command failed. See the pattern manager logs for more details.“,
“rc”: 1,
“request_id”: “1c844be316b74601853d2ddde595d94d”,
“stderr”: “Creating new client for cam-apache-1\nCreating new node for cam-apache-1\nConnecting to 0.0.0.0\nstty: ‘standard input’: Inappropriate ioctl for device\nstty: ‘standard input’: Inappropriate ioctl for device\nstty: ‘standard input’: Inappropriate ioctl for device”,
“stdout”: “0.0.0.0 knife sudo password: \nEnter your password: \r\n0.0.0.0 \r\n0.0.0.0 Sorry, try again.\r \n0.0.0.0 knife sudo password: \n0.0.0.0 \r\n0.0.0.0 Sorry, try again.\r\n0.0.0.0 knife sudo password: \n0.0.0.0 \r\n0.0.0.0 sudo: 3 incorrect password attempts”
}
You can import templates from GitHub or GitLab and deploy them. However, if you remove or change access token in GitHub or GitLab and then try to destroy instance, the operation fails with the following error message:
GithubClientError: vmware/terraform: failed to retrieve content list from github.; caused by {"message":"Not Found","documentation_url":"https://developer.github.com/v3"}
Ensure that the Managed services has a connection to GitHub/Gitlab when you destroy the instance.
CAM deployment stays in Progress - Log File repeating null_resource.clone_git: Still creating..."
The log file can record the template deployment status as in progress for a very long time. To identify the reason for the issue, do the following analysis on the deployed virtual machine wherein the problem occurred:
-
Run the following command to check whether your user has passwordless sudo:
sudo cat /etc/sudoersWhen it prompts for a password, enable passwordless sudo for the specific user.
-
If the user does not have sudo privileges, add that user to
/etc/sudoers. -
Run the following command to check if name server is set up in your machine:
ping github.com -
Check if the curl or Git commands are installed on the virtual machine. It might be an issue with the apt mirror.
SSL Certificate error while deploying a template.
To setup Git client locally:
-
Create
.gitconfigfile in the same Git repository as the template. The file should point to the correct CA certificates.[http] sslCAInfo = /home/terraform/certs/ca-bundle.crt -
When the provider Terraform deploys the template, it downloads the template and all its files from the Git repository, which includes the
.gitconfig. When the Terraform init is executed, the Git client looks up in the current folder (user's home folder for the current process) and it uses the appropriate CA certificates to download the modules from Git.