© 2004
Canonical Ltd.
•
Terms of use
•
Data privacy
•
Contact Launchpad Support
•
Blog
•
Careers
•
System status
•
4d1350f
(Get the code!)
We just saw this on a staging charmed kubernetes cluster. It happened when a discourse application and redis application were both on the same k8s worker that was on an OpenStack compute host that rebooted. The "fix" for now is to kill the discourse pod, at which point it sees the correct IP in relation data.