Bug 1334482
Summary: | neutron metadata ns proxy does not support ssl | ||
---|---|---|---|
Product: | Red Hat OpenStack | Reporter: | david.costakos |
Component: | openstack-neutron | Assignee: | Assaf Muller <amuller> |
Status: | CLOSED ERRATA | QA Contact: | Alexander Stafeyev <astafeye> |
Severity: | high | Docs Contact: | |
Priority: | high | ||
Version: | 8.0 (Liberty) | CC: | adahms, amuller, chrisw, david.costakos, jmelvin, jwinn, nyechiel, rahulsharmaait, srevivo |
Target Milestone: | async | Keywords: | Triaged, ZStream |
Target Release: | 8.0 (Liberty) | Flags: | david.costakos:
needinfo-
|
Hardware: | Unspecified | ||
OS: | Unspecified | ||
Whiteboard: | |||
Fixed In Version: | openstack-neutron-7.1.1-3.el7ost | Doc Type: | Bug Fix |
Doc Text: |
Previously, when SSL was enabled in the neutron metadata agent, the neutron metadata ns proxy would be unable to communicate to the neutron metadata agent via the Unix domain socket, and every request would result in a BadStatusLine error. This issue was resolved by disabling SSL in the local communication between the metadata agent and the metadata proxy over a Unix domain socket.
|
Story Points: | --- |
Clone Of: | Environment: | ||
Last Closed: | 2016-08-24 13:29:49 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: |
Description
david.costakos
2016-05-09 18:17:08 UTC
Upstream liberty backport is in progress. Assaf, it looks like the upstream fix was merged 6/08, any approximate date when this would be available? (In reply to Jeremy from comment #4) > Assaf, it looks like the upstream fix was merged 6/08, any approximate date > when this would be available? It's in openstack-neutron-7.1.1. What are the steps to configure metatdata ssl pls ? Verified code existence in openstack-neutron-7.1.1-3.el7ost on my machine. 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://rhn.redhat.com/errata/RHBA-2016-1770.html |