Bug 1433527 (ovnmetadata)
| Summary: | [RFE] [Neutron] [OVN] Metadata support | ||
|---|---|---|---|
| Product: | Red Hat OpenStack | Reporter: | Assaf Muller <amuller> |
| Component: | python-networking-ovn | Assignee: | Daniel Alvarez Sanchez <dalvarez> |
| Status: | CLOSED ERRATA | QA Contact: | Eran Kuris <ekuris> |
| Severity: | high | Docs Contact: | |
| Priority: | medium | ||
| Version: | 12.0 (Pike) | CC: | apevec, chrisw, dalvarez, ekuris, jlibosva, lhh, majopela, nyechiel, rhos-maint, sclewis, srevivo, tfreger |
| Target Milestone: | Upstream M3 | Keywords: | FutureFeature, Triaged |
| Target Release: | 13.0 (Queens) | ||
| Hardware: | Unspecified | ||
| OS: | Unspecified | ||
| Whiteboard: | |||
| Fixed In Version: | python-networking-ovn-4.0.0-0.20171205134230.746cae0.el7ost | Doc Type: | If docs needed, set a value |
| Doc Text: | Story Points: | --- | |
| Clone Of: | Environment: | ||
| Last Closed: | 2018-06-27 13:29:18 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: | 1498491, 1503796, 1548947 | ||
|
Description
Assaf Muller
2017-03-17 22:56:22 UTC
Will require OVS 2.8, pushed to OSP 13. The functionality was merged some time ago and as of today we have still pending some patches in TripleO [0]. Most of the work is done and we're close to finalize it soon. [0] https://review.openstack.org/#/q/topic:ovn-metadata-agent+(status:open+OR+status:merged) Patches upstream are merged: https://review.openstack.org/#/q/topic:ovn-metadata-agent+(status:open+OR+status:merged) Verified on: OSP13 p - 2018-04-26.3 python-networking-ovn-4.0.1-0.20180420150809.c7c16d4.el7ost.noarch test run: https://polarion.engineering.redhat.com/polarion/#/project/RHELOpenStackPlatform/testrun?id=20180430-0553 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-2018:2086 |