Harvester deployed Chart just creates a VM and waits for it to connect

[Mudrock1776]

Hey all, I need some help getting this chart to work. I have been running into problems at every step of this deployment, but currently I have the chart deploying a VM onto harvester, but then I get stuck on Configuring bootstrap node(s) waiting for agent to check in and apply initial plan. When I go into the VM I don't see any indication that rke2 has been installed on it or anything has even been done to it beyond just starting the machine up. When I go into that VM and manually install rke2 and connect it to rancher I am able to get it to connect without a problem. Is there something I need to implant in that QCOW2 VM image to get it to work? I can't find anything other than the qemu guest agents, which are already in the image. My values are:

cloudprovider: harvester

cloudCredentialSecretName: cattle-global-data:cc-npldd

kubernetesVersion: v1.31.7+rke2r1

cluster:
  name: test
# Specify nodepool options. Can add multiple node groups, specify etcd, controlplane and worker roles.
nodepools:
- etcd: true
  controlplane: true
  worker: true

  # specify node labels
  labels: {}

  # specify node taints
  taints: {}

  # specify nodepool size
  quantity: 1


  # Pause node pool
  # paused: false

  # specify displayName
  # displayName: ""

  # specify rolling update mechanism
  # rollingUpdate:
  #   The maximum number of machines that can be unavailable during the update.
  #   Value can be an absolute number (ex: 5) or a percentage of desired
  #   machines (ex: 10%).
  #   Absolute number is calculated from percentage by rounding down.
  #   This can not be 0 if MaxSurge is 0.
  #   Defaults to 0.
  #   Example: when this is set to 30%, the old MachineSet can be scaled
  #   down to 70% of desired machines immediately when the rolling update
  #   starts. Once new machines are ready, old MachineSet can be scaled
  #   down further, followed by scaling up the new MachineSet, ensuring
  #   that the total number of machines available at all times
  #   during the update is at least 70% of desired machines.
  #   maxUnavailable: "5"
  #   The maximum number of machines that can be scheduled above the
  #   desired number of machines.
  #   Value can be an absolute number (ex: 5) or a percentage of
  #   desired machines (ex: 10%).
  #   This can not be 0 if MaxUnavailable is 0.
  #   Absolute number is calculated from percentage by rounding up.
  #   Defaults to 1.
  #   Example: when this is set to 30%, the new MachineSet can be scaled
  #   up immediately when the rolling update starts, such that the total
  #   number of old and new machines do not exceed 130% of desired
  #   machines. Once old machines have been killed, new MachineSet can
  #   be scaled up further, ensuring that total number of machines running
  #   at any time during the update is at most 130% of desired machines.
  #   maxSurge: "1"

  # specify machineDeployment Labels
  # machineDeploymentLabels: {}

  # specify machineDeployment annotations
  # machineDeploymentAnnotations: {}

  name: pool1
  diskSize: 40
  diskBus: virtio
  cpuCount: 4
  memorySize: 8
  networkName: default/vlan145
  imageName: default/image-x5jqx #default/image-9fkgb
  vmNamespace: default
  sshUser: oms

The VM image I use is a Rocky 8 Linux machine with the certificates, proxy settings, and registries I use implanted in it.