My god... I've been having #microk8s cluster issues all week and I finally figured out that it's because of a failed auto-refresh of the core22 #snap

I've tried various approaches; clearing cache, removing downloaded snaps manually and I've been walking through the refresh again and nope - still fails to 'copy snap data'...

I know that disk space isn't an issue during the upgrade and the logs are terse so I'm really convinced I've no other path forward and that a rollback is warranted... BUT... Snapd won't allow me to revert the package because it's not currently active (because the upgrade failed)... Hurray! When an unattended upgrade fails, you're not allow to roll back!! Is that considered a desirable feature in a package manager?

If I can't find a safe way to restore this base-snap, I'll be forced to pursue more drastic measures which could result in loss of #k8s state and I'll need to rebuild my cluster... and I've literally been trying to work on disaster recovery for cluster when this all happened 😭

“AWS To Bare Metal Two Years Later: Answering Your Toughest Questions About Leaving AWS”, OneUptime (https://oneuptime.com/blog/post/2025-10-29-aws-to-bare-metal-two-years-later/view).

Via HN: https://news.ycombinator.com/item?id=45745281

On Lobsters: https://lobste.rs/s/ku4lrn/aws_bare_metal_two_years_later_answering

#AWS #Cloud #BareMetal #DIY #Savings #Kubernetes #MicroK8s #K8s