ci: nested PVE guests land in the ci pool with VMIDs 5081-5092

The runner token is pool-scoped (PVEVMAdmin on /pool/ci only), so VM.Allocate
succeeds only with pool_id set; VMIDs move into the 5000-5999 CI range.
This commit is contained in:
Clint Branham
2026-08-23 09:05:48 -05:00
parent c7eff18899
commit d3f05187dd
5 changed files with 15 additions and 6 deletions
+2
View File
@@ -137,6 +137,7 @@ jobs:
TF_VAR_disk_storage: ${{ vars.DISK_STORAGE }}
TF_VAR_iso_storage: ${{ vars.ISO_STORAGE }}
TF_VAR_network_bridge: ${{ vars.NETWORK_BRIDGE }}
TF_VAR_pool_id: ${{ vars.POOL_ID }}
run: bash ${SCRIPTS_DIR}/run-integration.sh provision
# ── Integration tests (self-hosted, per PVE version) ────────────────
@@ -215,6 +216,7 @@ jobs:
TF_VAR_disk_storage: ${{ vars.DISK_STORAGE }}
TF_VAR_iso_storage: ${{ vars.ISO_STORAGE }}
TF_VAR_network_bridge: ${{ vars.NETWORK_BRIDGE }}
TF_VAR_pool_id: ${{ vars.POOL_ID }}
# Always use force-cleanup in CI — handles corrupted state from
# cancelled runs, timeouts, or partial provisioning failures.
run: bash ${SCRIPTS_DIR}/run-integration.sh force-cleanup