Bug 894845
| Summary: | Resolve issues with the metadata service not working with overlapping IP ranges in Quantum | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Perry Myers <pmyers> |
| Component: | openstack-nova | Assignee: | Gary Kotton <gkotton> |
| Status: | CLOSED ERRATA | QA Contact: | yfried |
| Severity: | medium | Docs Contact: | |
| Priority: | medium | ||
| Version: | 2.0 (Folsom) | CC: | dallan, gkotton, jturner, ndipanov, sgordon |
| Target Milestone: | snapshot2 | ||
| Target Release: | 3.0 | ||
| Hardware: | All | ||
| OS: | Linux | ||
| Whiteboard: | |||
| Fixed In Version: | openstack-quantum-2013.1.1-9.el6ost | Doc Type: | Enhancement |
| Doc Text: |
Support for the OpenStack networking metadata proxy has been added to the compute service. This resolves a previous issue with the use of the metadata service in combination with having overlapping IP ranges defined in OpenStack networking.
|
Story Points: | --- |
| Clone Of: | Environment: | ||
| Last Closed: | 2013-06-11 18:54:41 UTC | Type: | --- |
| Regression: | --- | Mount Type: | --- |
| Documentation: | --- | CRM: | |
| Verified Versions: | Category: | --- | |
| oVirt Team: | --- | RHEL 7.3 requirements from Atomic Host: | |
| Cloudforms Team: | --- | Target Upstream Version: | |
| Embargoed: | |||
|
Description
Perry Myers
2013-01-13 20:17:25 UTC
Gary, do you have any additional information about what's going on here? When Quantum supports overlapping IP's there was a problem with the metadata service. This was addressed upstream by adding in a proxy from Quantum to the metadata service. The support was added in the Grizzly cycle https://blueprints.launchpad.net/quantum/+spec/metadata-overlapping-networks (In reply to Gary Kotton from comment #3) > The support was added in the Grizzly cycle > https://blueprints.launchpad.net/quantum/+spec/metadata-overlapping-networks Ok, I've moved this to POST since it should be in the builds now, if that's not correct, let me know. # rpm -qa | grep quan openstack-quantum-2013.1.1-9.el6ost.noarch # quantum net-list +--------------------------------------+-------------+-----------------------------------------------------+ | id | name | subnets | +--------------------------------------+-------------+-----------------------------------------------------+ | 0ba825dc-8bd4-405c-9696-6429cdf82dfb | ext_net_181 | 937520ec-aa6b-46a2-b305-cd82cc7acaf7 10.35.166.0/24 | | 8493539b-f795-442f-b591-103167ab172f | t2_net | 4840c5c5-0597-403f-ac46-3ddc7a0885a3 10.0.0.0/24 | | c7d4d7b7-804a-488a-ba50-e90dfbb6e18b | t1_net | dbf71206-db95-4e5a-ae3a-e09a8d3c1759 10.0.0.0/24 | +--------------------------------------+-------------+-----------------------------------------------------+ works from both tenants: $ wget http://169.254.169.254 Connecting to 169.254.169.254 (169.254.169.254:80) index.html 100% |*************************| 98 0:00:00 ETA 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. http://rhn.redhat.com/errata/RHBA-2013-0936.html |