Comment 3 for bug 1940627

This would be an issue for all the stable reactive charms at this point in time, the only available workaround would be to switch over to the -next charms that track the main branch (cs:~openstack-charmers-next/CHARM). There is of course risk involved in doing that as we are still in the development cycle and they have not received pre-release testing. So if this is for a production environment it would most likely be best to wait until the issue is resolved for all the reactive charms.