Skip to content

v0.15.3

Choose a tag to compare

View all tags
@github-actions github-actions released this 22 Apr 23:35
v0.15.3
This tag was signed with the committer’s verified signature.
Cliftonz Zac Clifton
SSH Key Fingerprint: kBE3PN8y73G0km42vo+O/iJR5ugoIx+G5am6Dad59pQ
Verified
Learn about vigilant mode.
bf57d3a
This commit was signed with the committer’s verified signature.
Cliftonz Zac Clifton
SSH Key Fingerprint: kBE3PN8y73G0km42vo+O/iJR5ugoIx+G5am6Dad59pQ
Verified
Learn about vigilant mode.

Fixes (Critical)

  • cleanupOrphanVMs now reads the request-id from the VM description instead of name-deriving it — The hourly orphan sweep was deleting healthy, newly-provisioned VMs because v0.15.0 changed the VM name format from omni_<requestID> to omni_<providerID>_<requestID> but the cleanup code still derived the expected request-id as strings.ReplaceAll(strings.TrimPrefix(name, "omni_"), "_", "-"). That produced truenas-talos-preview-control-planes-abc for a VM whose zvol was tagged org.omni:request-id=talos-preview-control-planes-abc — no match → flagged as orphan → stopped + deleted. Live impact: every v0.15+ cluster member was destroyed within an hour of provision finishing, log-visible as created VM → VM started → removing orphan VM (backing zvol not found) on the same VM ID. Fixed by parsing the request-id out of the VM description ("Managed by Omni infra provider (request-id: X)") via new meta.ParseRequestIDFromDescription — the description is the canonical store and is not affected by the name namespacing change. VMs without a parseable request-id are now skipped (legacy v0.14 look-alikes are safer as manual-cleanup than as accidental-delete). TestParseRequestIDFromDescription pins six parsing cases; existing TestCleanupOrphanVMs_* tests updated with description-bearing mocks. TestIntegration_OrphanVMCleanup skipped under replay until its cassette is re-recorded against a live TrueNAS.

Full Changelog: v0.15.2...v0.15.3

Assets 22
Loading