bridge status is not published as a service to the cloud in 1.1.0
Closed this issue · 1 comments
Describe the bug
thin-edge.io 1.1.0 no longer publishes the mosquitto-c8y-bridge service status to the cloud.
This is a breaking change, as the service was previously published and was useful when using multiple cloud connections, as you could monitor the status of the other clouds from a cloud with an active connection (e.g. monitor az from c8y, or vice versa).
To Reproduce
- Install thin-edge.io v1.1.0
- Configure to connect to Cumulocity IoT
- Open the Services page in the Device Management UI App
- Observe that a service named "mosquitto-c8y-bridge" is not present
Expected behavior
It is expected that the status of each bridge connection is sent to the configured clouds (if the bridge is up of course)
Screenshots
Below shows a screenshot from the v1.1.0 showing the missing service:
Downgrading to thin-edge.io 1.0.1 shows the service again:
Environment (please complete the following information):
| Property | Value |
|---|---|
| OS [incl. version] | Debian GNU/Linux 12 (bookworm) |
| Hardware [incl. revision] | unknown |
| System-Architecture | Linux 1c0d30ecf9f7 6.5.0-35-generic #35-Ubuntu SMP PREEMPT_DYNAMIC Sat Apr 27 00:18:38 UTC 2024 aarch64 GNU/Linux |
| thin-edge.io version | tedge 1.1.0 |
Additional context
QA has thoroughly checked the bug and here are the results:
-
Test for ticket exists in the test suite.
-
tests/RobotFramework/tests/cumulocity/service_monitoring/service_monitoring.robot
The test script is well-structured to verify the existence of an external identity and the status of the bridge service. -
QA has tested the bug and it's not reproducable anymore