In this post I will walk through the creation of VM clone from template using Terraform and vSphere provider. I have created a new VM with HCP Packer following the process in this post AlmaLinux 9 VM using HashiCorp Packer and vSphere ISO Plugin for AlmaLinux 9 or Ubuntu 24.04 VM using HashiCorp Packer and vSphere ISO Plugin for Ubuntu.
Prerequisites
Before starting, make sure you have the following tools installed:
- Terraform: Download and install from https://developer.hashicorp.com/terraform/install.
- Access to a vSphere environment with a vm template “almalinux_template”.
Directory Structure
Here is an example structure of the project:
almalinux-vm-clone/
├── main.tf
├── almalinux_ed25519
└── almalinux_ed25519.pubStep 1: Create the .tf template
In the begining of the template I define the necessary variables.
variable "vsphere_server" {
description = "vSphere server"
type = string
default = "10.3.2.20"
}
variable "vsphere_user" {
description = "vSphere username"
type = string
default = "[email protected]"
}
variable "vsphere_password" {
description = "vSphere password"
type = string
sensitive = true
default = "userpass"
}
variable "datacenter" {
description = "vSphere data center"
type = string
default = "MainDataCenter"
}
variable "host" {
description = "vSphere host"
type = string
default = "esxi.example.local"
}
variable "datastore" {
description = "vSphere datastore"
type = string
default = "ESXSystemStore"
}
variable "network_name" {
description = "vSphere network name"
type = string
default = "VM Network"
}
variable "vm_name" {
description = "VM name (ie: image_path)"
type = string
default = "almalinux_template"
}
variable "host_ip" {
description = "VM IP"
type = string
default = "10.3.2.5"
}
Next it is the configuration for the required vSphere provider. Providers are responsible for the API interaction. A provider is a plugin for Terraform that offers a collection of resource types.
terraform {
required_providers {
vsphere = {
source = "hashicorp/vsphere"
version = "2.4.0"
}
}
}
provider "vsphere" {
user = var.vsphere_user
password = var.vsphere_password
vsphere_server = var.vsphere_server
# If you have a self-signed cert
allow_unverified_ssl = true
}A data block defines the resources in vSphere environment that are going to be used for the new VM. We have to define the datacenter, datastore, ESXi host or cluster, network adapter and virtual machine name.
data "vsphere_datacenter" "datacenter" {
name = var.datacenter
}
data "vsphere_datastore" "datastore" {
name = var.datastore
datacenter_id = data.vsphere_datacenter.datacenter.id
}
data "vsphere_host" "host" {
name = var.host
datacenter_id = data.vsphere_datacenter.datacenter.id
}
data "vsphere_network" "network" {
name = var.network_name
datacenter_id = data.vsphere_datacenter.datacenter.id
}
data "vsphere_virtual_machine" "almalinux" {
name = "/${var.datacenter}/vm/${var.vm_name}"
datacenter_id = data.vsphere_datacenter.datacenter.id
}Each resource is associated with a single resource type, which determines the kind of infrastructure object it manages and what arguments and other attributes the resource supports. In the following example, the “vsphere_virtual_machine” resource type is named “almalinux-clone”. Each resource type is implemented by the provider.
resource "vsphere_virtual_machine" "almalinux-clone" {
name = "AlmaLinuxClone"
resource_pool_id = data.vsphere_host.host.resource_pool_id
datastore_id = data.vsphere_datastore.datastore.id
num_cpus = 2
memory = 1024
network_interface {
network_id = data.vsphere_network.network.id
}
wait_for_guest_net_timeout = 10
disk {
label = "disk0"
thin_provisioned = true
size = 32
}
guest_id = "rhel9_64Guest"
clone {
template_uuid = data.vsphere_virtual_machine.almalinux.id
customize {
linux_options {
host_name = "tfvmclone"
domain = "example.local"
}
network_interface {
ipv4_address = "10.3.2.5"
ipv4_netmask = 22
dns_server_list = ["10.3.2.1"]
}
ipv4_gateway = "10.3.2.1"
dns_server_list = ["10.3.2.1"]
dns_suffix_list = ["example.local"]
}
}
connection {
type = "ssh"
user = "almalinux"
private_key = file("./almalinux_ed25519")
host = vsphere_virtual_machine.almalinux-clone.default_ip_address
}
provisioner "remote-exec" {
inline = [
"sudo yum install git -y",
"sudo yum install htop -y"
]
}
}
output "vm_ip" {
value = vsphere_virtual_machine.almalinux-clone.guest_ip_addresses
}In resource block we define the total number of virtual processor cores that is optional, memory also is optional and a specification for a virtual disk device on the virtual machine that is required. Also a specification for a virtual NIC on the virtual machine that is required.
wait_for_guest_net_routable is required for the connection and remote-exec options if DHCP is enabled. In order to connect to the new VM it is necessary to wait for ip. It is the amount of time, in minutes, to wait for an available guest IP address on the virtual machine.
Under clone block the template_uuid defines the template is going to be cloned. As part of the clone operation, a virtual machine is customized to to the new host and network settings. Under customize block we define these parameters of the clone VM.
Step 2: Run terraform command
Now run terraform init command to setup the required providers.
> terraform init
Initializing the backend...
Initializing provider plugins...
- Finding hashicorp/vsphere versions matching "2.4.0"...
- Installing hashicorp/vsphere v2.4.0...
- Installed hashicorp/vsphere v2.4.0 (signed by HashiCorp)
Terraform has created a lock file .terraform.lock.hcl to record the provider
selections it made above. Include this file in your version control repository
so that Terraform can guarantee to make the same selections by default when
you run "terraform init" in the future.
Terraform has been successfully initialized!
You may now begin working with Terraform. Try running "terraform plan" to see
any changes that are required for your infrastructure. All Terraform commands
should now work.
If you ever set or change modules or backend configuration for Terraform,
rerun this command to reinitialize your working directory. If you forget, other
commands will detect it and remind you to do so if necessary.
Then run terraform apply command.
> terraform applyBellow is an output example of terraform apply command.
# terraform apply
data.vsphere_datacenter.datacenter: Reading...
data.vsphere_datacenter.datacenter: Read complete after 0s [id=datacenter-3]
data.vsphere_host.host: Reading...
data.vsphere_network.network: Reading...
data.vsphere_datastore.datastore: Reading...
data.vsphere_virtual_machine.almalinux: Reading...
data.vsphere_datastore.datastore: Read complete after 0s [id=datastore-14513]
data.vsphere_network.network: Read complete after 0s [id=network-13]
data.vsphere_virtual_machine.almalinux: Read complete after 0s [id=4211f4e0-ea34-8623-654c-eb8781d479cc]
data.vsphere_host.host: Read complete after 0s [id=host-14512]
Terraform used the selected providers to generate the following execution plan. Resource actions are indicated with the following symbols:
+ create
Terraform will perform the following actions:
# vsphere_virtual_machine.almalinux-clone will be created
+ resource "vsphere_virtual_machine" "almalinux-clone" {
+ annotation = (known after apply)
+ boot_retry_delay = 10000
+ change_version = (known after apply)
+ cpu_limit = -1
+ cpu_share_count = (known after apply)
+ cpu_share_level = "normal"
+ datastore_id = "datastore-14513"
+ default_ip_address = (known after apply)
+ ept_rvi_mode = "automatic"
+ extra_config_reboot_required = true
+ firmware = "bios"
+ force_power_off = true
+ guest_id = "rhel9_64Guest"
+ guest_ip_addresses = (known after apply)
+ hardware_version = (known after apply)
+ host_system_id = (known after apply)
+ hv_mode = "hvAuto"
+ id = (known after apply)
+ ide_controller_count = 2
+ imported = (known after apply)
+ latency_sensitivity = "normal"
+ memory = 1024
+ memory_limit = -1
+ memory_share_count = (known after apply)
+ memory_share_level = "normal"
+ migrate_wait_timeout = 30
+ moid = (known after apply)
+ name = "AlmaLinuxClone"
+ num_cores_per_socket = 1
+ num_cpus = 2
+ power_state = (known after apply)
+ poweron_timeout = 300
+ reboot_required = (known after apply)
+ resource_pool_id = "resgroup-14511"
+ run_tools_scripts_after_power_on = true
+ run_tools_scripts_after_resume = true
+ run_tools_scripts_before_guest_shutdown = true
+ run_tools_scripts_before_guest_standby = true
+ sata_controller_count = 0
+ scsi_bus_sharing = "noSharing"
+ scsi_controller_count = 1
+ scsi_type = "pvscsi"
+ shutdown_wait_timeout = 3
+ storage_policy_id = (known after apply)
+ swap_placement_policy = "inherit"
+ tools_upgrade_policy = "manual"
+ uuid = (known after apply)
+ vapp_transport = (known after apply)
+ vmware_tools_status = (known after apply)
+ vmx_path = (known after apply)
+ wait_for_guest_ip_timeout = 0
+ wait_for_guest_net_routable = true
+ wait_for_guest_net_timeout = 10
+ clone {
+ template_uuid = "4211f4e0-ea34-8623-654c-eb8781d479cc"
+ timeout = 30
+ customize {
+ dns_server_list = [
+ "10.3.2.1",
]
+ dns_suffix_list = [
+ "example.local",
]
+ ipv4_gateway = "10.3.2.1"
+ timeout = 10
+ linux_options {
+ domain = "example.local"
+ host_name = "tfvmclone"
+ hw_clock_utc = true
}
+ network_interface {
+ dns_server_list = [
+ "10.3.2.1",
]
+ ipv4_address = "10.3.2.5"
+ ipv4_netmask = 22
}
}
}
+ disk {
+ attach = false
+ controller_type = "scsi"
+ datastore_id = "<computed>"
+ device_address = (known after apply)
+ disk_mode = "persistent"
+ disk_sharing = "sharingNone"
+ eagerly_scrub = false
+ io_limit = -1
+ io_reservation = 0
+ io_share_count = 0
+ io_share_level = "normal"
+ keep_on_remove = false
+ key = 0
+ label = "disk0"
+ path = (known after apply)
+ size = 32
+ storage_policy_id = (known after apply)
+ thin_provisioned = true
+ unit_number = 0
+ uuid = (known after apply)
+ write_through = false
}
+ network_interface {
+ adapter_type = "vmxnet3"
+ bandwidth_limit = -1
+ bandwidth_reservation = 0
+ bandwidth_share_count = (known after apply)
+ bandwidth_share_level = "normal"
+ device_address = (known after apply)
+ key = (known after apply)
+ mac_address = (known after apply)
+ network_id = "network-13"
}
}
Plan: 1 to add, 0 to change, 0 to destroy.
Changes to Outputs:
+ vm_ip = (known after apply)
Do you want to perform these actions?
Terraform will perform the actions described above.
Only 'yes' will be accepted to approve.
Enter a value: yes
vsphere_virtual_machine.almalinux-clone: Creating...
vsphere_virtual_machine.almalinux-clone: Still creating... [10s elapsed]
vsphere_virtual_machine.almalinux-clone: Still creating... [20s elapsed]
vsphere_virtual_machine.almalinux-clone: Still creating... [30s elapsed]
vsphere_virtual_machine.almalinux-clone: Still creating... [40s elapsed]
vsphere_virtual_machine.almalinux-clone: Still creating... [50s elapsed]
vsphere_virtual_machine.almalinux-clone: Still creating... [1m0s elapsed]
vsphere_virtual_machine.almalinux-clone: Still creating... [1m10s elapsed]
vsphere_virtual_machine.almalinux-clone: Still creating... [1m20s elapsed]
vsphere_virtual_machine.almalinux-clone: Still creating... [1m30s elapsed]
vsphere_virtual_machine.almalinux-clone: Still creating... [1m40s elapsed]
vsphere_virtual_machine.almalinux-clone: Still creating... [1m50s elapsed]
vsphere_virtual_machine.almalinux-clone: Still creating... [2m0s elapsed]
vsphere_virtual_machine.almalinux-clone: Provisioning with 'remote-exec'...
vsphere_virtual_machine.almalinux-clone (remote-exec): Connecting to remote host via SSH...
vsphere_virtual_machine.almalinux-clone (remote-exec): Host: 10.3.2.5
vsphere_virtual_machine.almalinux-clone (remote-exec): User: almalinux
vsphere_virtual_machine.almalinux-clone (remote-exec): Password: false
vsphere_virtual_machine.almalinux-clone (remote-exec): Private key: true
vsphere_virtual_machine.almalinux-clone (remote-exec): Certificate: false
vsphere_virtual_machine.almalinux-clone (remote-exec): SSH Agent: false
vsphere_virtual_machine.almalinux-clone (remote-exec): Checking Host Key: false
vsphere_virtual_machine.almalinux-clone (remote-exec): Target Platform: unix
vsphere_virtual_machine.almalinux-clone (remote-exec): Connected!
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin --- B/s | 0 B --:-- ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin --- B/s | 0 B --:-- ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin 2.1 kB/s | 679 B 00:00 ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin 5.9 kB/s | 4.2 kB 00:00
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin --- B/s | 0 B --:-- ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin --- B/s | 0 B --:-- ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin 11 MB/s | 3.4 MB 00:00 ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin 11 MB/s | 11 MB 00:01
vsphere_virtual_machine.almalinux-clone: Still creating... [2m10s elapsed]
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin --- B/s | 0 B --:-- ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin --- B/s | 0 B --:-- ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin 7.7 kB/s | 3.8 kB 00:00
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin --- B/s | 0 B --:-- ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin --- B/s | 0 B --:-- ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin 17 MB/s | 5.1 MB 00:00 ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin 11 MB/s | 9.1 MB 00:00
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin --- B/s | 0 B --:-- ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin --- B/s | 0 B --:-- ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin 6.7 kB/s | 3.3 kB 00:00
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin --- B/s | 0 B --:-- ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin --- B/s | 0 B --:-- ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin 1.5 kB/s | 1.9 kB 00:00 ETA
vsphere_virtual_machine.almalinux-clone: Still creating... [2m20s elapsed]
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin 1.5 kB/s | 1.9 kB 00:00 ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin 1.5 kB/s | 1.9 kB 00:00 ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin 1.5 kB/s | 1.9 kB 00:00 ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin 1.5 kB/s | 1.9 kB 00:00 ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin 1.5 kB/s | 1.9 kB 00:00 ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin 1.5 kB/s | 1.9 kB 00:00 ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin 1.5 kB/s | 1.9 kB 00:00 ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin 1.5 kB/s | 1.9 kB 00:00 ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin 1.5 kB/s | 1.9 kB 00:00 ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin 1.5 kB/s | 1.9 kB 00:00 ETA
vsphere_virtual_machine.almalinux-clone: Still creating... [2m30s elapsed]
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin 1.5 kB/s | 1.9 kB 00:00 ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin 1.5 kB/s | 1.9 kB 00:00 ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin 1.5 kB/s | 1.9 kB 00:00 ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin 1.5 kB/s | 0 B 00:01 ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin 889 B/s | 13 kB 00:15
vsphere_virtual_machine.almalinux-clone (remote-exec): Extra P --- B/s | 0 B --:-- ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): Extra P --- B/s | 0 B --:-- ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): Extra P 88 kB/s | 37 kB 00:00 ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): Extra P 50 kB/s | 37 kB 00:00
vsphere_virtual_machine.almalinux-clone (remote-exec): Extra P --- B/s | 0 B --:-- ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): Extra P --- B/s | 0 B --:-- ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): Extra P 90 kB/s | 37 kB 00:00 ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): Extra P 88 kB/s | 57 kB 04:08 ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): Extra P 470 kB/s | 1.9 MB 00:45 ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): Extra P 2.6 MB/s | 13 MB 00:03 ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): Extra P 3.7 MB/s | 19 MB 00:01 ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): Extra P 9.9 MB/s | 23 MB 00:02
vsphere_virtual_machine.almalinux-clone: Still creating... [2m40s elapsed]
vsphere_virtual_machine.almalinux-clone: Still creating... [2m50s elapsed]
vsphere_virtual_machine.almalinux-clone: Still creating... [3m0s elapsed]
vsphere_virtual_machine.almalinux-clone (remote-exec): Dependencies resolved.
vsphere_virtual_machine.almalinux-clone (remote-exec): ========================================
vsphere_virtual_machine.almalinux-clone (remote-exec): Package Arch Version
vsphere_virtual_machine.almalinux-clone (remote-exec): Repo Size
vsphere_virtual_machine.almalinux-clone (remote-exec): ========================================
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing:
vsphere_virtual_machine.almalinux-clone (remote-exec): git x86_64 2.43.5-2.el9_5
vsphere_virtual_machine.almalinux-clone (remote-exec): appstream 50 k
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing dependencies:
vsphere_virtual_machine.almalinux-clone (remote-exec): git-core x86_64 2.43.5-2.el9_5
vsphere_virtual_machine.almalinux-clone (remote-exec): appstream 4.4 M
vsphere_virtual_machine.almalinux-clone (remote-exec): git-core-doc noarch 2.43.5-2.el9_5
vsphere_virtual_machine.almalinux-clone (remote-exec): appstream 2.7 M
vsphere_virtual_machine.almalinux-clone (remote-exec): perl-Error noarch 1:0.17029-7.el9
vsphere_virtual_machine.almalinux-clone (remote-exec): appstream 41 k
vsphere_virtual_machine.almalinux-clone (remote-exec): perl-Git noarch 2.43.5-2.el9_5
vsphere_virtual_machine.almalinux-clone (remote-exec): appstream 37 k
vsphere_virtual_machine.almalinux-clone (remote-exec): perl-TermReadKey
vsphere_virtual_machine.almalinux-clone (remote-exec): x86_64 2.38-11.el9
vsphere_virtual_machine.almalinux-clone (remote-exec): appstream 36 k
vsphere_virtual_machine.almalinux-clone (remote-exec): perl-lib x86_64 0.65-481.el9
vsphere_virtual_machine.almalinux-clone (remote-exec): appstream 13 k
vsphere_virtual_machine.almalinux-clone (remote-exec): Transaction Summary
vsphere_virtual_machine.almalinux-clone (remote-exec): ========================================
vsphere_virtual_machine.almalinux-clone (remote-exec): Install 7 Packages
vsphere_virtual_machine.almalinux-clone (remote-exec): Total download size: 7.2 M
vsphere_virtual_machine.almalinux-clone (remote-exec): Installed size: 38 M
vsphere_virtual_machine.almalinux-clone (remote-exec): Downloading Packages:
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin 3.7 MB/s | 0 B 00:06 ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): AlmaLin 3.7 MB/s | 0 B 00:06 ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): (1/7): --- B/s | 0 B --:-- ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): (1/7): 247 kB/s | 50 kB 00:00
vsphere_virtual_machine.almalinux-clone (remote-exec): (2-3/7) 247 kB/s | 50 kB 00:29 ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): (2/7): 945 kB/s | 41 kB 00:00
vsphere_virtual_machine.almalinux-clone (remote-exec): (3-4/7) 276 kB/s | 208 kB 00:25 ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): (3/7): 134 kB/s | 37 kB 00:00
vsphere_virtual_machine.almalinux-clone (remote-exec): (4-5/7) 1.0 MB/s | 3.8 MB 00:03 ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): (4/7): 1.3 MB/s | 36 kB 00:00
vsphere_virtual_machine.almalinux-clone (remote-exec): (5-6/7) 1.1 MB/s | 4.3 MB 00:02 ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): (5/7): 344 kB/s | 13 kB 00:00
vsphere_virtual_machine.almalinux-clone (remote-exec): (6-7/7) 1.2 MB/s | 5.0 MB 00:01 ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): (6/7): 6.1 MB/s | 4.4 MB 00:00
vsphere_virtual_machine.almalinux-clone (remote-exec): (7/7): 1.5 MB/s | 6.6 MB 00:00 ETA
vsphere_virtual_machine.almalinux-clone (remote-exec): (7/7): 3.1 MB/s | 2.7 MB 00:00
vsphere_virtual_machine.almalinux-clone (remote-exec): ----------------------------------------
vsphere_virtual_machine.almalinux-clone (remote-exec): Total 5.0 MB/s | 7.2 MB 00:01
vsphere_virtual_machine.almalinux-clone (remote-exec): Running transaction check
vsphere_virtual_machine.almalinux-clone (remote-exec): Transaction check succeeded.
vsphere_virtual_machine.almalinux-clone (remote-exec): Running transaction test
vsphere_virtual_machine.almalinux-clone (remote-exec): Transaction test succeeded.
vsphere_virtual_machine.almalinux-clone (remote-exec): Running transaction
vsphere_virtual_machine.almalinux-clone (remote-exec): Preparing : [= ] 1/1
vsphere_virtual_machine.almalinux-clone (remote-exec): Preparing : [=== ] 1/1
vsphere_virtual_machine.almalinux-clone (remote-exec): Preparing : [==== ] 1/1
vsphere_virtual_machine.almalinux-clone (remote-exec): Preparing : [====== ] 1/1
vsphere_virtual_machine.almalinux-clone (remote-exec): Preparing : [======= ] 1/1
vsphere_virtual_machine.almalinux-clone (remote-exec): Preparing : [========= ] 1/1
vsphere_virtual_machine.almalinux-clone (remote-exec): Preparing : 1/1
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : git-c [ ] 1/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : git-c [= ] 1/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : git-c [== ] 1/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : git-c [=== ] 1/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : git-c [==== ] 1/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : git-c [===== ] 1/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : git-core-2.4 1/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : git-c [ ] 2/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : git-c [= ] 2/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : git-c [== ] 2/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : git-c [=== ] 2/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : git-c [==== ] 2/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : git-c [===== ] 2/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : git-core-doc 2/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : perl- [ ] 3/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : perl- [=== ] 3/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : perl- [===== ] 3/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : perl-lib-0.6 3/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : perl- [ ] 4/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : perl- [= ] 4/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : perl- [=== ] 4/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : perl- [==== ] 4/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : perl- [===== ] 4/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : perl-TermRea 4/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : perl- [ ] 5/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : perl- [= ] 5/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : perl- [== ] 5/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : perl- [=== ] 5/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : perl- [===== ] 5/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : perl-Error-1 5/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : perl- [ ] 6/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : perl- [=== ] 6/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : perl- [===== ] 6/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : perl-Git-2.4 6/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : git-2 [ ] 7/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : git-2 [= ] 7/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : git-2 [== ] 7/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : git-2 [=== ] 7/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : git-2 [==== ] 7/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : git-2 [===== ] 7/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installing : git-2.43.5-2 7/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Running scriptlet: git-2.43.5-2 7/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Verifying : git-2.43.5-2 1/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Verifying : git-core-2.4 2/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Verifying : git-core-doc 3/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Verifying : perl-Error-1 4/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Verifying : perl-Git-2.4 5/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Verifying : perl-TermRea 6/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Verifying : perl-lib-0.6 7/7
vsphere_virtual_machine.almalinux-clone (remote-exec): Installed:
vsphere_virtual_machine.almalinux-clone (remote-exec): git-2.43.5-2.el9_5.x86_64
vsphere_virtual_machine.almalinux-clone (remote-exec): git-core-2.43.5-2.el9_5.x86_64
vsphere_virtual_machine.almalinux-clone (remote-exec): git-core-doc-2.43.5-2.el9_5.noarch
vsphere_virtual_machine.almalinux-clone (remote-exec): perl-Error-1:0.17029-7.el9.noarch
vsphere_virtual_machine.almalinux-clone (remote-exec): perl-Git-2.43.5-2.el9_5.noarch
vsphere_virtual_machine.almalinux-clone (remote-exec): perl-TermReadKey-2.38-11.el9.x86_64
vsphere_virtual_machine.almalinux-clone (remote-exec): perl-lib-0.65-481.el9.x86_64
vsphere_virtual_machine.almalinux-clone (remote-exec): Complete!
vsphere_virtual_machine.almalinux-clone: Still creating... [3m10s elapsed]
vsphere_virtual_machine.almalinux-clone (remote-exec): Last metadata expiration check: 0:00:36 ago on Wed Feb 5 12:22:05 2025.
vsphere_virtual_machine.almalinux-clone (remote-exec): Package htop-3.3.0-1.el9.x86_64 is already installed.
vsphere_virtual_machine.almalinux-clone (remote-exec): Dependencies resolved.
vsphere_virtual_machine.almalinux-clone (remote-exec): Nothing to do.
vsphere_virtual_machine.almalinux-clone (remote-exec): Complete!
vsphere_virtual_machine.almalinux-clone: Creation complete after 3m12s [id=42114129-660b-804b-04a8-d4fc49297c24]
Apply complete! Resources: 1 added, 0 changed, 0 destroyed.
Outputs:
vm_ip = tolist([
"10.3.2.5"
])