[Bug 1825843] Re: systemd issues with bionic-rocky causing nagios alert and can't restart daemon

2019-05-02 Thread Angel Vargas
Currently trying to get charm ceph-radosgw rev 268, Ubuntu Bionic, OpenStack Stein (base bundle like) I'm having the issue where the service seems running, then after few minutes the unit change to blocked and report the service is not running, this is in a baremetal deployment with multiples

[Bug 1825843] Re: systemd issues with bionic-rocky causing nagios alert and can't restart daemon

2019-04-23 Thread Angel Vargas
@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

[Bug 1825843] Re: systemd issues with bionic-rocky causing nagios alert and can't restart daemon

2019-04-22 Thread Angel Vargas
We upgraded the charms and radosgw got broken, ceph-radosgw release 267. After hours of debugging, We decided to test a fresh 4 node deployment to investigate the problem and try to revert, deploying a fresh openstack base juju is showing: ceph-radosgw/0* blocked idle