Drew Freiberger

I'm also running into this issue, and it's as Tom described, I've reinstalled microk8s and something has become detached from listening on port 80/443/whatever the ingress controller tries to work...

[inspection-report-20210709_142658.tar.gz](https://github.com/ubuntu/microk8s/files/6793575/inspection-report-20210709_142658.tar.gz) FYI, for support of 21.04 and later, microk8s inspect should use "ss" and "ip" commands instead of ifconfig and netstat.

I'd like to echo @peppepetra's suggestion for a caching mechanism to allow for an immediate return of a cached report with tunable metrics collection cycles happening in the background. I...

I've got a semi-related issue with regard to this and issue #362. On a juju 2.6.5 model, I'm having trouble with the dispatch fix from #362 after upgrading charm that's...

@erik78se Currently, the pattern is to use the StoredState and check changes of stored state (which you should only update after handling the tasks related to that config state change....

If I'm reading this right, and my new-found understanding of defer/emit/reemit is correct, the problem you have is order of operations. You defer the on_peer_joined, then you trigger on_grafana_relation_joined, which...

I think this may break tests, as it would no longer match 0 second sleep for leader unit, as the sleep would be bypassed as remaining = 0

updated leader test to expect no waiting.

Also this should apply to charmhelpers.fetch.giturl as well. git clone doesn't utilize the http/https proxy variables.

https://bugs.debian.org/cgi-bin/bugreport.cgi?bug=680891 appears to be the documentation culprit that may have lead to this code. https://bugs.launchpad.net/charm-swift-proxy/+bug/1817384 has more details on a specific incident with swift-proxy openstack upgrades that hits this issue.