The timing of that last occurrence coincides with the new wave of kubelet-eks snaps we released yesterday to fix LP:2023284. I suspect this auto-refresh error may happen every time we release updated snaps, and I don't think there's anything we can do within the snap to prevent it. Seems like either AMIs will need to be built with `snap refresh --hold kubelet-eks` to prevent the snap from auto-refreshing, or the bootstrap.sh script will need to catch errors from `snap set` and retry in case an auto-refresh is occurring.
The timing of that last occurrence coincides with the new wave of kubelet-eks snaps we released yesterday to fix LP:2023284. I suspect this auto-refresh error may happen every time we release updated snaps, and I don't think there's anything we can do within the snap to prevent it. Seems like either AMIs will need to be built with `snap refresh --hold kubelet-eks` to prevent the snap from auto-refreshing, or the bootstrap.sh script will need to catch errors from `snap set` and retry in case an auto-refresh is occurring.