Back to bug 2126725

Who When What Removed Added
Brendan Shephard 2022-09-14 10:56:39 UTC Keywords Triaged
Red Hat One Jira (issues.redhat.com) 2022-09-14 11:08:09 UTC Link ID Red Hat Issue Tracker OSP-18702
Brendan Shephard 2022-09-14 11:17:54 UTC Assignee rhos-maint bshephar
Miguel Lavalle 2022-09-26 13:55:45 UTC Priority unspecified medium
CC mlavalle
Brendan Shephard 2022-12-01 05:24:09 UTC Target Release --- 17.1
Fixed In Version openstack-tripleo-heat-templates-14.3.1-1.20221112021125.a628931.el9osttrunk.noarch.rpm
Target Milestone --- ga
Version 17.0 (Wallaby) 17.1(Wallaby)
Status NEW MODIFIED
RHEL Program Management 2022-12-01 05:24:32 UTC Target Release 17.1 --- --- 17.0
Lon Hohberger 2022-12-01 07:02:19 UTC Fixed In Version openstack-tripleo-heat-templates-14.3.1-1.20221112021125.a628931.el9osttrunk.noarch.rpm openstack-tripleo-heat-templates-14.3.1-1.20221112021125.a628931.el9osttrunk
Jon Schlueter 2022-12-08 21:00:13 UTC Flags needinfo?(bshephar)
Fixed In Version openstack-tripleo-heat-templates-14.3.1-1.20221112021125.a628931.el9osttrunk
CC jschluet
Jon Schlueter 2022-12-08 21:02:56 UTC Flags needinfo?(bshephar)
Status MODIFIED ASSIGNED
Brendan Shephard 2022-12-12 04:27:43 UTC Flags needinfo?(bshephar) needinfo?(bshephar)
Fixed In Version openstack-tripleo-heat-templates-14.3.1-1.20221112021125.a628931.el9osttrunk
Target Release 17.0 17.1
Status ASSIGNED MODIFIED
RHEL Program Management 2022-12-12 04:27:53 UTC Target Release 17.1 17.0
RHEL Program Management 2022-12-12 20:20:15 UTC Target Release 17.0 17.1
Lon Hohberger 2022-12-13 07:01:45 UTC Fixed In Version openstack-tripleo-heat-templates-14.3.1-1.20221112021125.a628931.el9osttrunk openstack-tripleo-heat-templates-14.3.1-1.20221118011425.fc038b6.el9ost
errata-xmlrpc 2022-12-14 10:11:17 UTC Status MODIFIED ON_QA
Andy Stillman 2023-05-31 21:04:30 UTC Flags needinfo?(bshephar)
Brendan Shephard 2023-06-01 04:27:42 UTC Doc Text Cause: Hard coded certificate location was ignoring user provided values.

Consequence:
Deployment with a custom cert location would leave services unable to retrieve information from API endpoints as TLS verification would fail.

Fix:
The change implemented ensures that user provided certificate locations are used during the deployment.
Flags needinfo?(bshephar)
Doc Type If docs needed, set a value Bug Fix
Jenny-Anne Lynch 2023-06-08 13:28:55 UTC CC jelynch
Doc Text Cause: Hard coded certificate location was ignoring user provided values.

Consequence:
Deployment with a custom cert location would leave services unable to retrieve information from API endpoints as TLS verification would fail.

Fix:
The change implemented ensures that user provided certificate locations are used during the deployment.
Before this update, hard-coded certificate location operated independently of user-provided values. During deployment with custom certificate locations, services did not retrieve information from API endpoints because Transport Layer Security (TLS) verification failed. With this update, user-provided certificate locations are used during deployment.
Jenny-Anne Lynch 2023-07-11 11:32:14 UTC CC jelynch
Maor 2023-08-02 14:28:00 UTC CC mblue
QA Contact jhakimra mblue
Maor 2023-08-09 13:40:00 UTC Status ON_QA ASSIGNED
Eran Kuris 2023-08-10 19:53:01 UTC Target Milestone ga z1
CC ekuris
Mike Burns 2023-08-11 13:59:33 UTC Target Milestone z1 z2
James Smith 2023-08-14 14:00:35 UTC CC jamsmith
Flags needinfo?(bshephar)
James Smith 2023-08-14 14:01:10 UTC Doc Type Bug Fix Known Issue
Doc Text Before this update, hard-coded certificate location operated independently of user-provided values. During deployment with custom certificate locations, services did not retrieve information from API endpoints because Transport Layer Security (TLS) verification failed. With this update, user-provided certificate locations are used during deployment. Hard-coded certificate location operates independently of user-provided values. During deployment with custom certificate locations, services do not retrieve information from API endpoints because Transport Layer Security (TLS) verification fails.

Back to bug 2126725