Is there a limitation on how many digits the custom vm id can be?

[nzsambo]

When running script in advanced mode, Is there a limitation on how many digits the custom vm id can be? 9999 works. 15000 does not. Fails to create container, I wanted to debug it before I raise any issue.

I get "Container creation failed, but template is not corrupted." Tried 2 different scripts, netbox and pocketbase.

Where can I look to troubleshoot, i.e. logs?

Here some relevant part of code I think, not much to go on.

create_lxc.sh

# Combine all options
PCT_OPTIONS=(${PCT_OPTIONS[@]:-${DEFAULT_PCT_OPTIONS[@]}})
[[ " ${PCT_OPTIONS[@]} " =~ " -rootfs " ]] || PCT_OPTIONS+=(-rootfs "$CONTAINER_STORAGE:${PCT_DISK_SIZE:-8}")

msg_info "Creating LXC Container"
if ! pct create "$CTID" "${TEMPLATE_STORAGE}:vztmpl/${TEMPLATE}" "${PCT_OPTIONS[@]}" &>/dev/null; then
  msg_error "Container creation failed. Checking if template is corrupted."

  if ! zstdcat "$TEMPLATE_PATH" | tar -tf - >/dev/null 2>&1; then
    msg_error "Template appears to be corrupted. Removing and re-downloading."
    rm -f "$TEMPLATE_PATH"

    if ! timeout 120 pveam download "$TEMPLATE_STORAGE" "$TEMPLATE" >/dev/null; then
      msg_error "Failed to re-download template."
      exit 208
    fi

    msg_ok "Re-downloaded LXC Template"

    if ! pct create "$CTID" "${TEMPLATE_STORAGE}:vztmpl/${TEMPLATE}" "${PCT_OPTIONS[@]}" &>/dev/null; then
      msg_error "Container creation failed after re-downloading template."
      exit 200
    fi
  else
    msg_error "Container creation failed, but template is not corrupted."
    exit 209
  fi
fi
msg_ok "LXC Container ${BL}$CTID${CL} ${GN}was successfully created."

[MickLesk]

3 to 9 digs.

the same script with id 9999 work, but with 10000 not?

[nzsambo]

1510X didn't work. I ran out of time to test 10000 thought i'd ask. Will report back

[nzsambo]

There were conflicting vm ids on another host in the cluster, my bad. It would be a good thing to output a reason when it fails

[MickLesk]

I can try to implement this