I can still see this issue on a different deployment. Again, the workaround is to downgrade to charm revision 31.
I can still see this issue on a different deployment. Again, the workaround is to downgrade to charm revision 31.