kaizen-agentic/engagements/pilots/eng-coulomb-railiance01-ho-001/reports/2026-07-21-capacity-recheck.md
tegwick 830276e46a
All checks were successful
CI Smoke / host-smoke (push) Successful in 0s
CI Smoke / container-smoke (push) Successful in 2s
ci / test (push) Successful in 2m31s
ops: capacity recheck railiance01 still 2 vCPU / 3.8 GiB
Operator 4/16 upgrade still not visible in guest as of 2026-07-21.
2026-07-21 04:14:47 +02:00

1.2 KiB
Raw Blame History

Capacity recheck — railiance01 — 2026-07-21

Engagement: eng-coulomb-railiance01-ho-001 Operator report (2026-07-16): VM upgraded to 4 vCPU / 16 GiB RAM Agent verify: ssh railiance01 at 2026-07-21 02:14 UTC

Result: still not visible in the guest OS

Resource Operator target Live guest
vCPU 4 2
RAM 16 GiB ~3.8 GiB (MemTotal 4009884 kB)
Swap our /swapfile 4 GiB, ~1.1 GiB used
Uptime — 4 days 13h (no recent resize reboot)
Hypervisor — KVM / OpenStack Nova
k3s node — Ready

Health snapshot

Metric Value Note
Load 1/5/15 ~1.6 / 3.2 / 4.0 Elevated vs 2 cores
MemAvailable ~571 Mi Tight
PSI memory full avg60 ~6% Pressure present
Disk / 57% of 96G OK
Top RSS k3s, gitea, state-hub uvicorn Same stack

Conclusion

The 4/16 flavor is still not applied (or not applied to this instance). Capacity risk from the original pilot remains open. Confirm flavor on 92.205.62.239 in the provider panel and complete any VERIFY_RESIZE / hard reboot.

ssh railiance01 'nproc; free -h'
# success criterion: nproc=4 and Mem ~15–16Gi