Bug 1686050 - Update version of AMQ Interconnect (metrics-qdr) from 1.2.0 to 1.3.0
Summary: Update version of AMQ Interconnect (metrics-qdr) from 1.2.0 to 1.3.0
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: qpid-proton
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
urgent
urgent
Target Milestone: z6
: 13.0 (Queens)
Assignee: Pradeep Kilambi
QA Contact: Leonid Natapov
URL:
Whiteboard:
Depends On:
Blocks: 1683729 1691507 1700789
TreeView+ depends on / blocked
 
Reported: 2019-03-06 15:36 UTC by Leif Madsen
Modified: 2019-04-30 17:23 UTC (History)
8 users (show)

Fixed In Version: openstack-qdrouterd-container-13.0-1 openstack-collectd-container-13.0-65 qpid-proton-0.26.0-3.el7
Doc Type: Rebase: Enhancements Only
Doc Text:
Rebase package(s) to version: openstack-qdrouterd-container-13.0-1 Rebase the qdrouter images to support the version with edge mode enabled by default.
Clone Of:
: 1700788 1700789 (view as bug list)
Environment:
Last Closed: 2019-04-30 17:23:45 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:0926 0 None None None 2019-04-30 17:23:55 UTC

Comment 7 Jon Schlueter 2019-04-16 16:01:05 UTC 
adding qpid-proton only to OSP 13, container images are going to rely on content sets for qpid-dispatch and libwebsockets to pull in right versions.
Comment 9 Jon Schlueter 2019-04-16 17:41:44 UTC 
included in openstack-qdrouterd-container-13.0-1 and openstack-collectd-container-13.0-65
Comment 14 Leonid Natapov 2019-04-22 10:12:07 UTC 
Deployed latest OSP13 with metrics_qdr container.

from the /var/log/containers/metrics-qdr/metrics-qdr.log

2019-04-22 09:42:27.542861 +0000 SERVER (info) Container Name: Router.controller-0.localdomain
2019-04-22 09:42:27.542969 +0000 ROUTER (info) Router started in Edge mode
2019-04-22 09:42:27.542980 +0000 ROUTER (info) Version: Red Hat AMQ Interconnect 1.3.0 (qpid-dispatch 1.5.0)
2019-04-22 09:42:27.556547 +0000 AGENT (info) Activating management agent on $_management_internal
2019-04-22 09:42:27.556729 +0000 ROUTER_CORE (info) Core module enabled: edge_router
2019-04-22 09:42:27.556780 +0000 ROUTER_CORE (info) Core module present but disabled: core_test_hooks
2019-04-22 09:42:27.556791 +0000 ROUTER_CORE (info) Core module present but disabled: edge_addr_tracking
2019-04-22 09:42:27.556801 +0000 ROUTER_CORE (info) Core module present but disabled: address_lookup_server
2019-04-22 09:42:27.556810 +0000 ROUTER_CORE (info) Core module enabled: address_lookup_client
2019-04-22 09:42:27.556817 +0000 ROUTER_CORE (info) Router Core thread running. 0/Router.controller-0.localdomain
2019-04-22 09:42:27.556825 +0000 ROUTER_CORE (info) In-process subscription M/$management
2019-04-22 09:42:27.556856 +0000 ROUTER_CORE (info) In-process subscription L/$management
2019-04-22 09:42:27.556867 +0000 ROUTER_CORE (info) In-process subscription L/$_management_internal
2019-04-22 09:42:27.557223 +0000 POLICY (info) Policy configured maxConnections: 65535, policyDir: '',access rules enabled: 'false', use hostname patterns: 'false'
2019-04-22 09:42:27.558275 +0000 POLICY (info) Policy fallback defaultVhost is defined: '$default'
2019-04-22 09:42:27.558625 +0000 CONN_MGR (info) Configured Listener: 172.17.1.32:5666 proto=any, role=normal
2019-04-22 09:42:27.563889 +0000 SERVER (notice) Operational, 4 Threads Running (process ID 1)
2019-04-22 09:42:27.564675 +0000 SERVER (notice) Listening on 172.17.1.32:5666
2019-04-22 09:58:09.705367 +0000 SERVER (info) [1]: Accepted connection to 172.17.1.32:5666 from 172.17.1.32:55430
-----
Red Hat AMQ Interconnect 1.3.0 (qpid-dispatch 1.5.0)
Comment 18 errata-xmlrpc 2019-04-30 17:23:45 UTC 
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, 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-2019:0926
Note You need to log in before you can comment on or make changes to this bug.