Bug 2040605

Summary: RHOSP 16.2 qdrouterd image ships an old version of qpid-dispatch
Product: Red Hat OpenStack Reporter: Miguel Garcia <mgarciac>
Component: openstack-containersAssignee: Miguel Garcia <mgarciac>
Status: CLOSED WONTFIX QA Contact: Leonid Natapov <lnatapov>
Severity: medium Docs Contact: Joanne O'Flynn <joflynn>
Priority: medium    
Version: 16.1 (Train)CC: achernet, lmadsen, m.andre
Target Milestone: ---Keywords: Triaged
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Before this update, the Service Telemetry Framework (STF) client could not connect to the STF server, because the latest version of Red Hat AMQ Interconnect does not allow TLS connections without a CA certificate. + This update corrects this problem by providing a new Orchestration service (heat) parameter, `MetricsQdrSSLProfiles`. + To obtain a Red Hat OpenShift TLS certificate, enter these commands: + ---- $ oc get secrets $ oc get secret/default-interconnect-selfsigned -o jsonpath='{.data.ca\.crt}' | base64 -d ---- + Add the `MetricsQdrSSLProfiles` parameter with the contents of your Red Hat OpenShift TLS certificate to a custom environment file: + ---- MetricsQdrSSLProfiles: - name: sslProfile caCertFileContent: | -----BEGIN CERTIFICATE----- ... TOpbgNlPcz0sIoNK3Be0jUcYHVMPKGMR2kk= -----END CERTIFICATE----- ---- + Then, redeploy your overcloud with the `openstack overcloud deploy` command.
 Story Points: ---
Clone Of: 1949169 Environment:
Last Closed: 2022-05-26 16:13:18 UTC Type: ---
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Embargoed:
Bug Depends On: 1949168, 1949169, 1982764, 2075122, 2116323, 2129165    
Bug Blocks:    

Description Miguel Garcia 2022-01-14 08:34:32 UTC 
+++ This bug was initially created as a clone of Bug #1949169 +++

RHOSP 16.2 qdrouterd image ships an old version of qpid-dispatch.

It should be adjusted to ship the latest version available from AMQ-Interconnect.
Comment 13 Leif Madsen 2022-05-26 16:13:18 UTC 
Had a conversation and unless there is a required need to update this (other than it's awkward that OSP13 has a newer version), then we're in favour of leaving this as-is and only maintaining the grades for this particular release. If this happens to get cross-tag / bumped in the future then the templating engine is able to deal with this, and documentation simply needs to be updated to reflect the new system.

There should be no need to update this component release in OSP 16.2. Closing > Won't Fix.