I checked logging on our side - I couldn't find a Sentry report matching the error's timestamp, which suggests either this was a problem at the haproxy level (Sentry only logs application units), or it was a non- loggable error (403 is an example, I'm not saying it was the case here, but the circumstances under which most 4xx errors are returned to clients are normal enough that we don't log them).
Unfortunately, due to the amount of traffic the store gets, we only have 15 days' retention of haproxy logs, meaning that the possible haproxy error that happened on the 12th of May has now rotated into /dev/null :( I'll check other logs we might have to try to learn more. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1928182 Title: Unable to deploy postgresql-k8s charm from charmhub To manage notifications about this bug go to: https://bugs.launchpad.net/juju/+bug/1928182/+subscriptions -- ubuntu-bugs mailing list [email protected] https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
