I've heard that a linked-clone pool can break if someone deletes the snapshot it depends on. Aren't old snapshots generally supposed to be cleaned up? How should that be handled in Horizon?
Can deleting an old snapshot break a Horizon linked-clone pool?
Answers
Yes. A linked-clone pool can depend on a snapshot of its parent image, so snapshot age alone is not a safe reason to delete it. The normal advice to keep ordinary VM snapshots under control doesn't account for that dependency.
Before cleaning up, check which parent image and snapshot each pool uses. Don't assume an old snapshot is unused just because it has been around for months.
Reply to this answer
If the goal is to retire an old image, prepare and verify a new image and snapshot, then move the affected pool to it using the appropriate Horizon workflow. Check that no pools or other derivatives still depend on the old snapshot before removing it.
Test that process outside production first. The exact steps depend on the Horizon version and pool configuration, so check the applicable product documentation rather than treating snapshot deletion as routine housekeeping.
Reply to this answer
If the snapshot is already gone and the pool is broken, pause further cleanup and work out what image and snapshot the pool was using. Depending on the configuration, moving the pool to a valid snapshot or building a replacement pool may be options, but neither should be assumed to be a quick fix.
Check the version-specific recovery procedure and involve someone with Horizon experience before making more changes.
Reply to this answer
I wouldn't jump straight from this mistake to a verdict about someone's overall skills. A person used to standard VMs might apply a reasonable snapshot cleanup habit in the wrong place. Still, checking dependencies before deleting infrastructure is a basic safeguard, and changes like this need review and a test environment.
Reply to this answer
Add your answer
Answers are reviewed before publication.
q.468+tinratchet:
That dependency check matters even if one pool has already moved. Another pool could still be using the old image.