-
Bug
-
Resolution: Done
-
Major
-
Global Hub 1.7.0
-
None
-
Quality / Stability / Reliability
-
1
-
False
-
-
False
-
-
-
GH Train-36, GH Train-37
-
Important
-
None
Description of problem:
RHACM4K-43020: HoH: As a globalhub admin, I can get the managed hub cluster agent status from database when this managed hub agent status is changed [e2e, status]
/home/ubuntu/workspace/globalhub-e2e/pkg/test/e2e/managedhub_status_test.go:71 STEP: check the cluster acmqe-hoh-auto-gkhclh status in status.leaf_hub_heartbeats table @ 01/23/26 03:10:16.32 STEP: disable the globalhub agent on regional hub acmqe-hoh-auto-gkhclh @ 01/23/26 03:10:16.364
I0123 03:10:16.562869 14167 localpolicy_test.go:482] wait for heart beats status to inactive using 5 seconds STEP: check the data in table local_spec.policies @ 01/23/26 03:10:16.602
[FAILED] in [It] - /home/ubuntu/workspace/globalhub-e2e/pkg/test/e2e/managedhub_status_test.go:135 @ 01/23/26 03:20:16.603 STEP: enable the globalhub agent on regional hub acmqe-hoh-auto-gkhclh @ 01/23/26 03:20:16.812
I0123 03:21:44.207197 14167 localpolicy_test.go:522] wait for heart beats status to active using 5 seconds
I0123 03:21:49.208196 14167 localpolicy_test.go:522] wait for heart beats status to active using 10 seconds
I0123 03:21:54.583136 14167 localpolicy_test.go:522] wait for heart beats status to active using 15 seconds
manager pod log:
2026-01-23T03:23:17.893Z INFO event.localrootpolicy common/util.go:21 unknown compliance status: Unknown2026-01-23T03:23:20.720Z INFO hubmanagement/hub_addon_controller.go:67 inactive the agent when the global hub addon(acmqe-hoh-auto-kq68fb) is deleted2026-01-23T03:23:20.720Z INFO hubmanagement/hub_management.go:124 inactive the hub {"name": "acmqe-hoh-auto-kq68fb"}2026-01-23T03:23:40.995Z INFO acmqe-hoh-auto-gkhclh.complete.managedhub.info conflator/element_complete.go:68 resetting complete element processed version {"version": "0.1"}
2026/01/23 03:24:10 /workspace/manager/pkg/processes/hubmanagement/hub_management.go:104 dial tcp 172.30.43.46:5432: connect: connection refused[2.829ms] [rows:0] SELECT * FROM "status"."leaf_hub_heartbeats" WHERE last_timestamp < '2026-01-23 03:19:10.569' AND status = 'active'2026-01-23T03:24:10.572Z ERROR hubmanagement/hub_management.go:91 dial tcp 172.30.43.46:5432: connect: connection refusedfailed to update the hub statusgithub.com/stolostron/multicluster-global-hub/manager/pkg/processes/hubmanagement.(*HubManagement).Start.func1 /workspace/manager/pkg/processes/hubmanagement/hub_management.go:912026-01-23T03:24:56.715Z INFO controller/controller.go:106 reconcile transport(producer/consumer): mgh/transport-config2026-01-23T03:24:56.716Z INFO controller/controller.go:130 kafka credential is updated, reconciling consumer and producer2026-01-23T03:24:56.716Z INFO consumer/generic_consumer.go:172 transport consumer with cloudevents-kafka receiver2026-01-23T03:24:56.718Z INFO consumer/generic_consumer.go:136 start receiving events: test_custom_prefixzdwmwnglobal_hub2026-01-23T03:24:56.721Z INFO consumer/generic_consumer.go:207 init consumer with database offsets {"offsets": [{"Topic":"gh-status.acmqe-hoh-auto-hqvzj7","Partition":0,"Offset":18,"Metadata":null,"Error":null,"LeaderEpoch":null},{"Topic":"gh-status.acmqe-hoh-auto-gkhclh","Partition":0,"Offset":160,"Metadata":null,"Error":null,"LeaderEpoch":null}]}2026-01-23T03:24:56.721Z INFO cloudevents v2@v2.0.0-20251125184210-ee1cae0e0f5d/protocol.go:166 Subscribing to topics: [^gh-status.*]
Version-Release number of selected component (if applicable):
How reproducible:
Steps to Reproduce:
- ...