Bug 1696332
| Summary: | zaqar does not support ipv6 endpoint | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Gurenko Alex <agurenko> | ||||||||
| Component: | openstack-zaqar | Assignee: | RHOS Maint <rhos-maint> | ||||||||
| Status: | CLOSED ERRATA | QA Contact: | Gurenko Alex <agurenko> | ||||||||
| Severity: | high | Docs Contact: | |||||||||
| Priority: | high | ||||||||||
| Version: | 13.0 (Queens) | CC: | apevec, bdobreli, emacchi, jjoyce, jschluet, jslagle, lhh, mgeary, ohochman, rrasouli, slinaber, tvignaud | ||||||||
| Target Milestone: | z7 | Keywords: | Triaged, ZStream | ||||||||
| Target Release: | 13.0 (Queens) | ||||||||||
| Hardware: | Unspecified | ||||||||||
| OS: | Unspecified | ||||||||||
| Whiteboard: | |||||||||||
| Fixed In Version: | openstack-zaqar-6.0.1-3.el7ost | Doc Type: | Release Note | ||||||||
| Doc Text: |
This update provides OpenStack Messaging Service (zaqar) support for IPv6 endpoints, to facilitate an Undercloud deployed with IPv6.
|
Story Points: | --- | ||||||||
| Clone Of: | |||||||||||
| : | 1702715 (view as bug list) | Environment: | |||||||||
| Last Closed: | 2019-07-10 13:06:00 UTC | Type: | Bug | ||||||||
| 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: | 1702715, 1714205, 1718343, 1721595 | ||||||||||
| Bug Blocks: | |||||||||||
| Attachments: |
|
||||||||||
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. Created attachment 1552063 [details]
1551924: openstack overcloud deploy running with --debug
Sorry, I've attached wrong log file, please have a look at a new one
Created attachment 1555188 [details]
overcloud deploy output on a new puddle
Seems like the problem was more than just parsing IPv6 address properly, I'm attaching output of overcloud deploy command with --debug parameter on a new puddle that includes initial fix
it looks like we at least need this patch to python-websocket-client as well: https://github.com/websocket-client/websocket-client/commit/6bc909be0ebe12d6843b64b242e0f015084a7df5 cannot be verified due to: https://bugzilla.redhat.com/show_bug.cgi?id=1718343 https://bugzilla.redhat.com/show_bug.cgi?id=1721595 Verified on puddle 2019-06-28.1 [stack@undercloud-0 ~]$ rpm -q openstack-zaqar openstack-zaqar-6.0.1-4.el7ost.noarch zaqar-websocket public endpoint successfully set to the IPv6 address. 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:1739 |
Created attachment 1551924 [details] openstack overcloud deploy running with --debug 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: