mirror of
https://github.com/mulgadc/spinifex.git
synced 2026-11-06 10:58:16 +00:00
1c39e29367
* test: pin guest poweroff handling and stopped-instance volume state * test: gofmt the poweroff and stopped-volume tests * test: pin start after detach, one-poll poweroff, reattach of released volumes and the delete refusal * test: separate the embedded mounter from the recorder fields * fix: end a guest poweroff as a stop and keep stopped instances' data volumes attached A clean QEMU exit after the heartbeat saw the guest power off now stops the instance instead of waiting for crash detection. Unmount no longer releases data volumes. DetachVolume on a stopped instance edits the record, then releases the volume. Starting an instance stopped on an older build drops data volumes that are attached elsewhere or deleted and fails on a missing boot volume. * fix: keep the stopped-instance detach inside the instance service file and format start reconcile * docs: describe guest poweroff, stopped-instance volumes and detach on a stopped instance * fix: allow detaching the root volume of a stopped instance and refuse a start with no root volume as AWS does * feat: attach volumes to a stopped instance and fix root-detach start fixtures * docs: describe attach and root detach on a stopped instance * test: Unmount seals only and leaves every attached volume in-use Changed with the person's explicit approval, relayed by dev-design on 11-03. EBS root and data volumes persist across stop on AWS, so stop and crash unmount no longer release any attached volume. * docs: note that the EFI variable store cannot be detached from a stopped instance * test: unmount contract tests expect no volume state write on stop * test: order imports in stopped-volume daemon tests * refactor: drop the unused volume state updater from the volume mounter