fix(recovery): apply windows 99 vmware autostart truth
Some checks failed
CD Pipeline / workflow-shape (push) Has been cancelled
CD Pipeline / cancel-stale-cd (push) Has been cancelled
CD Pipeline / tests (push) Has been cancelled
CD Pipeline / build-and-deploy (push) Has been cancelled
CD Pipeline / post-deploy-checks (push) Has been cancelled
Some checks failed
CD Pipeline / workflow-shape (push) Has been cancelled
CD Pipeline / cancel-stale-cd (push) Has been cancelled
CD Pipeline / tests (push) Has been cancelled
CD Pipeline / build-and-deploy (push) Has been cancelled
CD Pipeline / post-deploy-checks (push) Has been cancelled
This commit is contained in:
@@ -1,3 +1,24 @@
|
||||
## 2026-07-01 — 13:11 P0-7 Windows 99 VMware autostart controlled apply
|
||||
|
||||
**照主線修正的問題**:
|
||||
- 99 runtime readback 已從 RDP console 補齊:`wooo-super\administrator`、`vmrun_present=True`、`vmrun_path=C:\Program Files (x86)\VMware\VMware Workstation\vmrun.exe`。
|
||||
- 99 Apply 前實際 `vmrun list` 為 5 台 VM:`192.168.0.110_Ubuntu_64-bit_DevOps`、`192.168.0.188_Ubuntu_64-bit_AI`、`192.168.0.120_Ubuntu_64-bit_K3s`、`192.168.0.121_Ubuntu_64-bit_K3s`、`192.168.0.112_KALI-Linux`;`192.168.0.111` ping 可達,但 99 上沒有任何 `111` VMX,故標記為 `host111_vmware_target=missing_no_vmx_found_on_99_ping_only`,不能假裝 111 由 99 VMware 管理。
|
||||
- 已在 99 controlled apply 建立 / 覆蓋 `AWOOOI-Start-VMware-VMs` SYSTEM startup task:`task_state=Ready`、`task_action_execute=powershell.exe`、`args=-NoProfile -ExecutionPolicy Bypass -File "C:\ProgramData\AWOOOI\Start-AWOOOI-VMs.ps1"`、`task_principal=SYSTEM runlevel=Highest`。
|
||||
- 已寫入 `C:\ProgramData\AWOOOI\Start-AWOOOI-VMs.ps1`,並以正式 repo source 重套一次;順序為 `110 -> 188 -> 120 -> 121 -> 112`;startup script 會先啟動 VMware auth / DHCP service,若 VM 已在 `vmrun list` 內則輸出 `VM_ALREADY_RUNNING` 並跳過,避免重複 start。
|
||||
- 已套用 Windows Update no-auto-reboot policy:`NoAutoRebootWithLoggedOnUsers=1`、`AlwaysAutoRebootAtScheduledTime=0`、`AUOptions=3`、`ScheduledInstallDay=0`、`ScheduledInstallTime=3`、`AUPowerManagement=0`。
|
||||
- repo source `scripts/reboot-recovery/windows99-vmware-autostart.ps1` 已同步 99 真實 layout:新增 `Host110Vmx`、`RequiredVmAliases`、`D:\Documents\Virtual Machines` / `D:\Downloads` discovery roots、known VMX candidates、displayName matching 與 `VM_ALREADY_RUNNING` skip 行為。
|
||||
|
||||
**runtime verifier**:
|
||||
- `task_present=1`、`task_state=Ready`、`start_script_present=1`、`start_script_bytes=1441`、`wu_policy_present=1`、`vmrun_present=1`。
|
||||
- `vmrun_list=Total running VMs: 5`,且 `ping_192.168.0.110=True`、`ping_192.168.0.111=True`、`ping_192.168.0.112=True`、`ping_192.168.0.120=True`、`ping_192.168.0.121=True`、`ping_192.168.0.188=True`。
|
||||
- Windows Security 右下角曾提示 `Controlled Folder Access` 對 `vmrun.exe` 的封鎖提醒;本輪未點擊、未放寬 Defender/Controlled Folder Access,需在下一次真實 99 reboot 或 approved reboot drill 觀察 startup task 是否被攔截。
|
||||
|
||||
**仍維持**:
|
||||
- 沒有讀 secret / token / `.env` / raw sessions / SQLite / auth;沒有使用 GitHub / `gh` / GitHub API;沒有重啟主機,沒有 Docker / Nginx / K3s / DB restart,沒有 firewall / Defender policy 放寬。
|
||||
|
||||
**下一步**:
|
||||
- 回到 ordered P0:重跑 all-host cold-start / SLO scorecard;110 仍是 `harbor_110_remote_ssh_publickey_auth_stalled` + Harbor / registry `502` 主 blocker,若 110 SSH/control path 恢復,第一動作仍是套用新版 systemd exporter 或暫停舊 exporter,再回讀 systemd/logind、Gitea CPU 與 load5/core。
|
||||
|
||||
## 2026-07-01 — 13:05 AI Loop current blocker 對齊 publickey offer timeout / load-not-high
|
||||
|
||||
**照主線修正的問題**:
|
||||
|
||||
Reference in New Issue
Block a user