Fix storage pool activation for sushy-tools VM power control

Resolves deployment failures where Ironic nodes reach 'deploy failed' state
because VMs cannot be powered on via Redfish.

Root cause: Storage pools (e.g., oooq_pool) existed but were inactive, causing
sushy-tools to fail with 'Storage pool not found' errors when attempting to
power on VMs. This resulted in HTTP 500 errors on ComputerSystem.Reset actions.

Fixes:
- Ensure storage pool is started when found by path
- Ensure storage pool is started when reused by name
- Always refresh pool so libvirt sees all volumes
- Critical for sushy-tools BMC emulator to access VM disks

Without this fix, VMs stay powered off and Ironic deployment fails.

Author: eliorerz

scripts/provision_landing_zone.sh

@@ -191,6 +191,14 @@ if ! sudo virsh pool-uuid "$POOL_NAME" > /dev/null 2>&1; then
         # A pool exists for our path - use it regardless of name
         info "Found existing pool '$EXISTING_POOL' using path $POOL_PATH, will use it"
         POOL_NAME="$EXISTING_POOL"
+
+        # Ensure the pool is started (it might be inactive)
+        if ! sudo virsh pool-info "$POOL_NAME" | grep -q "State:.*running"; then
+            info "Starting inactive pool '$POOL_NAME'..."
+            sudo virsh pool-start "$POOL_NAME"
+        fi
+        sudo virsh pool-autostart "$POOL_NAME" 2>/dev/null || true
+        info "✓ Storage pool '$POOL_NAME' is active"
     else
         # No pool exists for our path - create one
         info "No pool found for path $POOL_PATH, creating pool '$POOL_NAME'..."
@@ -219,8 +227,18 @@ EOF
     fi
 else
     info "Using existing storage pool: $POOL_NAME"
+    # Ensure the pool is started (it might be inactive)
+    if ! sudo virsh pool-info "$POOL_NAME" | grep -q "State:.*running"; then
+        info "Starting inactive pool '$POOL_NAME'..."
+        sudo virsh pool-start "$POOL_NAME"
+    fi
+    sudo virsh pool-autostart "$POOL_NAME" 2>/dev/null || true
 fi
 
+# Refresh the pool so libvirt sees all volumes (important for sushy-tools)
+info "Refreshing storage pool '$POOL_NAME'..."
+sudo virsh pool-refresh "$POOL_NAME"
+
 # Check if pool is active, start it if not
 if ! sudo virsh pool-info "$POOL_NAME" 2>/dev/null | grep -qE "State:[[:space:]]+running$"; then
     info "Storage pool is inactive, starting it..."