bpg
commented
1 year ago Hey @joace! 👋🏼
The provider does not have any insights in what the remote-exec provisioner is doing, it is executed at the end of the creation phase when the resource (a VM) is created as specified by the template. The resource state is captured at that moment as well, before executing external provisioners.
I think it would be possible to do a similar config via cloud-init, without remote-exec.
For example, one of my test box is configured like this:
data "local_file" "ssh_public_key" {
filename = "./id_rsa.pub"
}
resource "proxmox_virtual_environment_file" "cloud_config" {
content_type = "snippets"
datastore_id = "local"
node_name = var.virtual_environment_node_name
source_raw {
data = <<EOF
#cloud-config
users:
- default
- name: ubuntu
groups:
- sudo
shell: /bin/bash
ssh_authorized_keys:
- ${trimspace(data.local_file.ssh_public_key.content)}
sudo: ALL=(ALL) NOPASSWD:ALL
runcmd:
- apt update
- apt install -y qemu-guest-agent net-tools mc curl apt-transport-https vim git wget gnupg2 software-properties-common lsb-release ca-certificates uidmap
- timedatectl set-timezone America/Toronto
- systemctl enable qemu-guest-agent
- systemctl start qemu-guest-agent
- swapoff -a
- ........ keep going ....
EOF
file_name = "cloud-config.yaml"
}
}
resource "proxmox_virtual_environment_vm" "node" {
vm_id = 9300
name = "template-ubuntu-23.04-k8s-1.27.1"
node_name = var.virtual_environment_node_name
description = "Ubuntu 23.04 with k8s 1.27.1"
agent {
enabled = true
}
cpu {
cores = 2
type = "host"
}
memory {
dedicated = 8192
}
disk {
datastore_id = "fast"
interface = "scsi0"
file_id = proxmox_virtual_environment_file.ubuntu_cloud_image.id
size = 32
}
initialization {
ip_config {
ipv4 {
address = "dhcp"
}
}
// note: cloud-init config is required to enable user agent
user_data_file_id = proxmox_virtual_environment_file.cloud_config.id
}
network_device {
bridge = "vmbr2"
}
}
resource "proxmox_virtual_environment_file" "ubuntu_cloud_image" {
content_type = "iso"
datastore_id = "local"
node_name = var.virtual_environment_node_name
source_file {
path = "http://cloud-images.ubuntu.com/lunar/current/lunar-server-cloudimg-amd64.img"
}
}You can also have cloud-init config in an external file, as in this example.
I have no extra NICs in those, but you can check with https://cloudinit.readthedocs.io/en/latest/reference/network-config-format-v2.html how to configure some.
joace
Describe the bug Used provider 1.8.0 on proxmox to clone some new VM from an existing MicroOS template, as unknown issue in MicroOS, can't use cloud-init to configure new VMs, so used "file" and "remote-exec" provisioner to copy a network manager profile activate connection, (specifically assign a static IP on 2nd NIC - eth1, 1st NIC -eth0 still working with DHCP), but after all configuration successfully completed, the assigned IP not populated in generated tfstate file even the target host already had NIC connected, had to run "terraform apply -refresh-only" to get it updated.
Actually, I have another local_file resource to generate ansible host inventory file based on provisioned target, since "ipv4_addresses" list doesn't have valid IP for eth1, it's empty, so the resource execution would fail.
Is this the expected behavior with this provider? If so, is there better way refresh state inside the configuration, just before "local_file" resource?
To Reproduce Steps to reproduce the behavior:
Create a resource 'proxmox_virtual_environment_vm' with below provisioners:
The new VM had the correct IPs assigned to both NIC
The output of VM attribute ipv4_addresses missing the IP on 2nd NIC
If I manually run terraform apply -refresh-only, the output will be updated with all IPs included:
node_ipv4_addresses = [ tolist([ tolist([ "127.0.0.1", ]), tolist([ "10.14.76.58", ]), tolist([ "192.168.1.65", ]), ]), tolist([ tolist([ "127.0.0.1", ]), tolist([ "10.14.76.59", ]), tolist([ "192.168.1.70", ]), ]), ]
initialization { datastore_id = var.disk_storage dns { domain = var.dns_domain } ip_config { ipv4 { address = "dhcp" } } ip_config { ipv4 { address = "${cidrhost(local.cluster_subnet, ((count.index+1) <= local.cluster_deployed_server_node ? (count.index+1) : (count.index+1-local.cluster_deployed_server_node+var.cluster_max_server_node)))}/${local.private_network_masknum}" } } user_account { keys = [file(var.ssh_public_key_file)] username = var.normal_user_name password = var.normal_user_password } }
Terraform v1.4.5 on linux_amd64