Bug 1229655
Summary: | VNC Console failed to load with IPv6 Addresses | |||
---|---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | Udi Shkalim <ushkalim> | |
Component: | openstack-nova | Assignee: | Sahid Ferdjaoui <sferdjao> | |
Status: | CLOSED ERRATA | QA Contact: | Udi Shkalim <ushkalim> | |
Severity: | medium | Docs Contact: | ||
Priority: | medium | |||
Version: | 7.0 (Kilo) | CC: | adahms, berrange, dasmith, eglynn, kchamart, ndipanov, nyechiel, oblaut, pbrady, sbauza, sferdjao, sgordon, ssainkar, vromanso, yeylon | |
Target Milestone: | ga | |||
Target Release: | 7.0 (Kilo) | |||
Hardware: | x86_64 | |||
OS: | Linux | |||
Whiteboard: | ||||
Fixed In Version: | openstack-nova-2015.1.0-12.el7ost | Doc Type: | Bug Fix | |
Doc Text: |
When deploying an OpenStack environment that uses IPv6, VNC consoles would fail to load and an exception was raised to the client because the websocketproxy was unable to verify the origin header - "handler exception: Origin header does not match this host.”
With this release, the code in websocketproxy has been updated to handle IPv6. As a result, users can now successfully connect to VNC consoles when all services are configured to use IPv6.
|
Story Points: | --- | |
Clone Of: | ||||
: | 1229669 (view as bug list) | Environment: | ||
Last Closed: | 2015-08-05 13:25:13 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: | ||||
Bug Blocks: | 1083896, 1229669 |
Description
Udi Shkalim
2015-06-09 10:58:43 UTC
This was filled as part of the IPv6 testing. The patch seems to be working properly, hence this BZ to track the inclusion in OSP-7. Verified the fix locally on an IPv6 environment 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/RHEA-2015:1548 |