Bug 2107487 - "openstack stack show" command fails because Heat returns HTTPS URL for HTTP endpoint
Summary: "openstack stack show" command fails because Heat returns HTTPS URL for HTTP ...
Keywords:
Status: CLOSED NOTABUG
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: puppet-tripleo
Version: 16.1 (Train)
Hardware: All
OS: All
medium
medium
Target Milestone: ---
: ---
Assignee: Antonio Romito
QA Contact: David Rosenfeld
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2022-07-15 08:25 UTC by Alex Stupnikov
Modified: 2023-08-04 07:20 UTC (History)
10 users (show)

Fixed In Version:
Doc Type: No Doc Update
Doc Text:
Clone Of:
Environment:
Last Closed: 2023-03-09 14:03:49 UTC
Target Upstream Version:
Embargoed:


Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Issue Tracker OSP-17630 0 None None None 2022-07-15 08:54:47 UTC

Description Alex Stupnikov 2022-07-15 08:25:30 UTC
Description of problem:

SSL error [1] is raised when running "openstack stack show NAME" command: OpenStack Client fails to establish SSL connection to 8004 port. We analyzed service catalog, but there are no HTTPS endpoints for orchestration service there.

We also collected problematic command's output in debug mode and figured out that this problem is caused by Heat control plane's response to find stack request: location header contains https:// URL, while message contains http:// URL.

https://docs.openstack.org/api-ref/orchestration/v1/index.html?expanded=find-stack-detail#find-stack

We kindly ask you to help us understand this problem. I will provide detailed outputs and information about collected data privately.

[1]
SSL exception connecting to https://IP:8004/v1/SUFFIX: HTTPSConnectionPool(host='IP', port=8004): Max retries exceeded with url: SUFFIX (Caused by SSLError(SSLError(1, '[SSL: WRONG_VERSION_NUMBER] wrong version number (_ssl.c:897)'),))


Version-Release number of selected component (if applicable):
RHOSP 16.1.3


Note You need to log in before you can comment on or make changes to this bug.