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 0/lxd/0 10.100.0.61 80/tcp
Services not running that should be:
ceph-rado...@rgw.juju-168b18-0-lxd-0
if we do a restart to the lxd container, when we execute:
sudo service radosgw status
we get:
Apr 23 00:18:05 juju-168b18-0-lxd-0 radosgw[36885]: Starting
client.rgw.juju-168b18-0-lxd-0...
Apr 23 00:18:05 juju-168b18-0-lxd-0 systemd[1]: Started LSB: radosgw RESTful
rados gateway.
Apr 23 00:19:22 juju-168b18-0-lxd-0 systemd[1]: Stopping LSB: radosgw RESTful
rados gateway...
Apr 23 00:19:22 juju-168b18-0-lxd-0 systemd[1]: Stopped LSB: radosgw RESTful
rados gateway.
Apr 23 00:19:26 juju-168b18-0-lxd-0 systemd[1]: radosgw.service: Failed to
reset devices.list: Operation not permitted
Apr 23 00:19:26 juju-168b18-0-lxd-0 systemd[1]: Starting LSB: radosgw RESTful
rados gateway...
Apr 23 00:19:26 juju-168b18-0-lxd-0 radosgw[37618]: Starting
client.rgw.juju-168b18-0-lxd-0...
Apr 23 00:19:26 juju-168b18-0-lxd-0 systemd[1]: Started LSB: radosgw RESTful
rados gateway.
Apr 23 00:21:48 juju-168b18-0-lxd-0 systemd[1]: Stopping LSB: radosgw RESTful
rados gateway...
Apr 23 00:21:49 juju-168b18-0-lxd-0 systemd[1]: Stopped LSB: radosgw RESTful
rados gateway.
that's the output after a fresh boot, then if we do:
sudo service radosgw start
we get the service running:
● radosgw.service - LSB: radosgw RESTful rados gateway
Loaded: loaded (/etc/init.d/radosgw; generated)
Active: active (running) since Tue 2019-04-23 00:22:47 UTC; 17min ago
Docs: man:systemd-sysv-generator(8)
Process: 811 ExecStart=/etc/init.d/radosgw start (code=exited,
status=0/SUCCESS)
Tasks: 582 (limit: 7372)
CGroup: /system.slice/radosgw.service
└─850 /usr/bin/radosgw -n client.rgw.juju-168b18-0-lxd-0
Apr 23 00:22:46 juju-168b18-0-lxd-0 systemd[1]: Starting LSB: radosgw RESTful
rados gateway...
Apr 23 00:22:46 juju-168b18-0-lxd-0 radosgw[811]: Starting
client.rgw.juju-168b18-0-lxd-0...
Apr 23 00:22:47 juju-168b18-0-lxd-0 systemd[1]: Started LSB: radosgw RESTful
rados gateway.
but juju still keep showing the unit blocked.
This is the juju log for ceph-radosgw:
https://paste.ubuntu.com/p/kb3g9XZ7nb/
We are getting the same behaviour in our production and test
environment. Even if we get the service running, the unit doesn't seem
to work from the openstack perspective, e.g. try to create a bucket the
api doesn't connect.
How can I help?
--
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
