@james-page In my case, after the upgrade the charm unit showed running, but the openstack api/horizon wasn't able to talk to the service, we went to the logs and there wasn't obvious information telling why the service wasn't up, only from the juju controller logs we saw for some reason the radosgw was going to failed state, after reboot the container, the service wasn't starting, so we decide to deploy a lean openstack-base r59 (bionic-stein) bundle as usual, so the charm was showing the exact same problem/behavior. Not sure what is wrong with the update we did, to get back radosgw working we have to downgrade to (bionic-rocky):
ceph-mon 13.2.4+dfsg1 active 3 ceph-mon jujucharms 32 ubuntu ceph-osd 13.2.4+dfsg1 active 3 ceph-osd jujucharms 275 ubuntu ceph-radosgw 13.2.4+dfsg1 active 1 ceph-radosgw jujucharms 263 ubuntu And we got the services up again. We are currently working to fix the production environment. When I wrote first time, I thought the initial way how the bug affect us was related to the current report. -- You received this bug notification because you are a member of Ubuntu Bugs, which is subscribed to Ubuntu. https://bugs.launchpad.net/bugs/1825843 Title: systemd issues with bionic-rocky causing nagios alert and can't restart daemon To manage notifications about this bug go to: https://bugs.launchpad.net/charm-ceph-radosgw/+bug/1825843/+subscriptions -- ubuntu-bugs mailing list ubuntu-bugs@lists.ubuntu.com https://lists.ubuntu.com/mailman/listinfo/ubuntu-bugs
