Comment 10 for bug 1987331

Hi folks, I've had a 1.29 env up for a few weeks now that has completed the 1.29.(0...3) snap refreshes without issue (no rogue kubectl processes; no snap refresh errors in debug-log). I suspect the `ignore_running` fix coupled with our new pattern for reconciling states in 1.29+ has solved this [0].

That said, comment 7 with kubectl-3117 suggests this could still affect releases < 1.29. I'm removing the 1.29 milestones and setting this bug to 'incomplete' for now; if this is still affecting folks, let us know the snapd and charmed k8s versions and we'll triage a different milestone as needed.

[0] https://github.com/charmed-kubernetes/charm-kubernetes-control-plane/blob/release_1.29/src/charm.py#L484-L485