RHEL Engineering is moving the tracking of its product development work on RHEL 6 through RHEL 9 to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "RHEL project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs in the statuses "NEW", "ASSIGNED", and "POST" are being migrated throughout September 2023. Bugs of Red Hat partners with an assigned Engineering Partner Manager (EPM) are migrated in late September as per pre-agreed dates. Bugs against components "kernel", "kernel-rt", and "kpatch" are only migrated if still in "NEW" or "ASSIGNED". If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "RHEL project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/RHEL-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
Bug 1702715 - websocket-client doesn't pack hostnames, breaking ipv6 support in openstack-zaqar
Summary: websocket-client doesn't pack hostnames, breaking ipv6 support in openstack-z...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat Enterprise Linux 7
Classification: Red Hat
Component: python-websocket-client
Version: 7.6
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: rc
: ---
Assignee: Lokesh Mandvekar
QA Contact: atomic-bugs@redhat.com
URL:
Whiteboard:
Depends On: 1714205
Blocks: 1696332 1718343
TreeView+ depends on / blocked
 
Reported: 2019-04-24 14:34 UTC by Lon Hohberger
Modified: 2023-09-14 05:27 UTC (History)
20 users (show)

Fixed In Version: python-websocket-client-0.56.0-1.git3c25814.el7
Doc Type: If docs needed, set a value
Doc Text:
Clone Of: 1696332
: 1714205 1718343 (view as bug list)
Environment:
Last Closed: 2019-06-04 19:10:15 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
Red Hat Product Errata RHBA-2019:1353 0 None None None 2019-06-04 19:10:18 UTC

Description Lon Hohberger 2019-04-24 14:34:00 UTC 
+++ This bug was initially created as a clone of Bug #1696332 +++

Description of problem: When trying to deploy pre-deployed servers and setting public endpoints to ipv6, deployment cannot start due to zaqar websocket returning 504


Version-Release number of selected component (if applicable):
OSP13
puddle: 2019-03-18.1


How reproducible: 100%


Steps to Reproduce:
1. Set public endpoints to IPv6 address
2. Start overcloud deployment

Actual results:

Overcloud installation fails even before stack creation starts (see log attached)

Expected results:

Overcloud installation starts successfully

Additional info:

--- Additional comment from Emilien Macchi on 2019-04-04 15:53:27 UTC ---

I don't see where Zaqar fails, however I see:

2019-04-02 12:04:04,679 INFO: Failed to discover available identity versions when contacting https://2001:db8::b2:13000/. Attempting to parse version from URL.
2019-04-02 12:04:04,680 INFO: Could not determine a suitable URL for the plugin
2019-04-02 12:04:04,724 INFO: + openstack quota set --cores -1 --instances -1 --ram -1
2019-04-02 12:04:05,450 INFO: Failed to discover available identity versions when contacting https://2001:db8::b2:13000/. Attempting to parse version from URL.
2019-04-02 12:04:05,450 INFO: Could not determine a suitable URL for the plugin


Please update the BZ with sosreport.



[snip]

--- Additional comment from James Slagle on 2019-04-23 14:56:01 UTC ---

it looks like we at least need this patch to python-websocket-client as well:

https://github.com/websocket-client/websocket-client/commit/6bc909be0ebe12d6843b64b242e0f015084a7df5
Comment 1 Lon Hohberger 2019-04-24 14:34:33 UTC 
python-websocket-client is part of RHEL Extras
Comment 3 Lon Hohberger 2019-04-30 19:52:57 UTC 
Not sure - adding jslagle
Comment 12 Gurenko Alex 2019-05-26 08:17:33 UTC 
 As per mailing thread, this package fails QE since it requires the workaround: export WEBSOCKET_CLIENT_CA_BUNDLE=/etc/pki/ca-trust/extracted/pem/tls-ca-bundle.pem otherwise deployment fails at the beginning with [SSL: CERTIFICATE_VERIFY_FAILED] certificate verify failed (_ssl.c:618) error message. Once worked around though the deployment passes further with web sockets endpoint set to IPv6
Comment 15 errata-xmlrpc 2019-06-04 19:10:15 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:1353
Comment 20 Adriano Petrich 2019-06-06 10:56:23 UTC 
*** Bug 1717469 has been marked as a duplicate of this bug. ***
Comment 23 Red Hat Bugzilla 2023-09-14 05:27:28 UTC 
The needinfo request[s] on this closed bug have been removed as they have been unresolved for 1000 days
Note You need to log in before you can comment on or make changes to this bug.