Comment 1 for bug 2025285

I spoke with Pedro about this and it seems that apt was in the process list running on the machines when this condition occurred. As stated in the juju log it was trying to install necessary packages. But I also understand from him that it wasn't finishing and restarting the machines unstuck it. It would be nice if this condition occurs again to have the logs from apt to see why it was stuck. Fundamentally this isn't something the charm can do much about unless there's some kind of preparation that apt needs from the charm.

I suppose it's POSSIBLE apt is blocked waiting on some kind of human input?

The next steps would be from charmed-kubernetes to attempt to reproduce in a different environment.

@pedrovlf was this on focal or jammy?