Bug 1976981
| Summary: | [regression] qdstat --connections no longer works for QDR | ||
|---|---|---|---|
| Product: | Service Telemetry Framework | Reporter: | Leif Madsen <lmadsen> |
| Component: | service-telemetry-operator-container | Assignee: | Leif Madsen <lmadsen> |
| Status: | CLOSED ERRATA | QA Contact: | Leonid Natapov <lnatapov> |
| Severity: | high | Docs Contact: | Joanne O'Flynn <joflynn> |
| Priority: | high | ||
| Version: | 1.3 | CC: | pleimer |
| Target Milestone: | z1 | Keywords: | Regression, Triaged, ZStream |
| Target Release: | 1.3 (STF) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | service-telemetry-operator-container-1.3.4-1 | Doc Type: | Bug Fix |
| Doc Text: |
Before this update, port 5672 was not enabled for AMQ Interconnect when deploying an Interconnect cluster with Service Telemetry Framework (STF) 1.3. As a result, administrators were not able to query with qdstat for connections to validate their deployment.
With this update, port 5672 was added to the list of listeners in the Interconnect object that is managed by the AMQ Interconnect Operator. Administrators can now use qdstat to validate and debug AMQ Interconnect.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2021-07-19 14:16:01 UTC | Type: | Bug |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Leif Madsen
2021-06-28 16:54:00 UTC
Will result in console output like the following without fix:
oc -n service-telemetry exec -it default-interconnect-855df69b95-hh9rq -- qdstat --connections
ConnectionException: Connection amqp://0.0.0.0:amqp/$management disconnected: Condition('proton.pythonio', 'Connection refused to all addresses')
command terminated with exit code 1
Since the problem described in this bug report should be resolved in a recent advisory, it has been closed with a resolution of ERRATA. For information on the advisory (Release of components for Service Telemetry Framework v1.3.1), and where to find the updated files, follow the link below. If the solution does not work for you, open a new bug report. https://access.redhat.com/errata/RHBA-2021:2771 |