The resolution of this bug is blocking the implementation of a smart check for the Designate services in the openstack-service-checks charm
https://bugs.launchpad.net/charm-openstack-service-checks/+bug/1845293
We can still reproduce the bug in cloud:bionic-rocky:
All services are up:
$ date Tue Sep 24 11:01:10 UTC 2019
$ openstack dns service list +--------------------------------------+---------------+--------------+--------+-------+--------------+ | id | hostname | service_name | status | stats | capabilities | +--------------------------------------+---------------+--------------+--------+-------+--------------+ | bac409d2-6be5-4f0a-bed6-14ace02f91ef | juju-e719f5-9 | api | UP | - | - | | f1b39c47-23a1-430f-a5b2-0bd5f9a8f3e8 | juju-e719f5-9 | producer | UP | - | - | | 6103d503-6ecb-4a31-82a9-814948c5f667 | juju-e719f5-9 | mdns | UP | - | - | +--------------------------------------+---------------+--------------+--------+-------+--------------+
We stopped the mdns service and after 30 minutes it is still reported as UP even if the heartbeat is 30 minutes old:
$ date Tue Sep 24 11:36:12 UTC 2019
$ openstack dns service show 6103d503-6ecb-4a31-82a9-814948c5f667 +----------------+--------------------------------------+ | Field | Value | +----------------+--------------------------------------+ | capabilities | - | | created_at | 2019-09-23T16:24:48.000000 | | heartbeated_at | 2019-09-24T11:06:03.000000 | | hostname | juju-e719f5-9 | | id | 6103d503-6ecb-4a31-82a9-814948c5f667 | | service_name | mdns | | stats | - | | status | UP | | updated_at | 2019-09-24T11:06:03.000000 | +----------------+--------------------------------------+
Is there any news on the resolution of it?
The resolution of this bug is blocking the implementation of a smart check for the Designate services in the openstack- service- checks charm
https:/ /bugs.launchpad .net/charm- openstack- service- checks/ +bug/1845293
We can still reproduce the bug in cloud:bionic-rocky:
All services are up:
$ date
Tue Sep 24 11:01:10 UTC 2019
$ openstack dns service list ------- ------- ------- ------- ----+-- ------- ------+ ------- ------- +------ --+---- ---+--- ------- ----+ ------- ------- ------- ------- ----+-- ------- ------+ ------- ------- +------ --+---- ---+--- ------- ----+ 6be5-4f0a- bed6-14ace02f91 ef | juju-e719f5-9 | api | UP | - | - | 23a1-430f- a5b2-0bd5f9a8f3 e8 | juju-e719f5-9 | producer | UP | - | - | 6ecb-4a31- 82a9-814948c5f6 67 | juju-e719f5-9 | mdns | UP | - | - | ------- ------- ------- ------- ----+-- ------- ------+ ------- ------- +------ --+---- ---+--- ------- ----+
+------
| id | hostname | service_name | status | stats | capabilities |
+------
| bac409d2-
| f1b39c47-
| 6103d503-
+------
We stopped the mdns service and after 30 minutes it is still reported as UP even if the heartbeat is 30 minutes old:
$ date
Tue Sep 24 11:36:12 UTC 2019
$ openstack dns service show 6103d503- 6ecb-4a31- 82a9-814948c5f6 67 ------- ---+--- ------- ------- ------- ------- ------- + ------- ---+--- ------- ------- ------- ------- ------- + 23T16:24: 48.000000 | 24T11:06: 03.000000 | 6ecb-4a31- 82a9-814948c5f6 67 | 24T11:06: 03.000000 | ------- ---+--- ------- ------- ------- ------- ------- +
+------
| Field | Value |
+------
| capabilities | - |
| created_at | 2019-09-
| heartbeated_at | 2019-09-
| hostname | juju-e719f5-9 |
| id | 6103d503-
| service_name | mdns |
| stats | - |
| status | UP |
| updated_at | 2019-09-
+------
Is there any news on the resolution of it?