Bug 1539788 - Getting rhosp13/openstack-neutron-metadata-agent-ovn rhosp13/openstack-neutron-server-ovn into OSP13
Summary: Getting rhosp13/openstack-neutron-metadata-agent-ovn rhosp13/openstack-neutro...
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Red Hat OpenStack
Classification: Red Hat
Component: openstack-containers
Version: 13.0 (Queens)
Hardware: Unspecified
OS: Unspecified
high
high
Target Milestone: beta
: 13.0 (Queens)
Assignee: Daniel Alvarez Sanchez
QA Contact: Eran Kuris
Andrew Burden
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2018-01-29 15:49 UTC by Daniel Alvarez Sanchez
Modified: 2018-06-28 08:01 UTC (History)
6 users (show)

Fixed In Version: openstack-neutron-server-ovn-docker-13.0-1 openstack-neutron-metadata-agent-ovn-docker-13.0-1
Doc Type: No Doc Update
Doc Text:
undefined
Clone Of:
Environment:
Last Closed: 2018-06-28 08:00:49 UTC
Target Upstream Version:
Embargoed:

Attachments (Terms of Use)


Links
System ID Private Priority Status Summary Last Updated
OpenStack gerrit 511225 0 None MERGED Add Dockerfile for networking-ovn-metadata-agent 2020-08-05 13:55:27 UTC
OpenStack gerrit 525182 0 None MERGED Add OVN Metadata Agent to containerized environments 2020-08-05 13:55:27 UTC
Red Hat Product Errata RHEA-2018:2085 0 None None None 2018-06-28 08:01:57 UTC

Description Daniel Alvarez Sanchez 2018-01-29 15:49:12 UTC 
In OSP13 we need to have the following container images to use from OVN backend:

* rhosp13/openstack-neutron-server-ovn
* rhosp13/openstack-neutron-metadata-agent-ovn
Comment 2 Daniel Alvarez Sanchez 2018-01-29 16:00:04 UTC 
This is the series of patches that implement this feature:

https://review.openstack.org/#/q/topic:ovn-metadata-agent+(status:open+OR+status:merged)
Comment 14 Eran Kuris 2018-06-20 10:29:22 UTC 
Verified on OSP13  -p 2018-06-19.2

192.168.24.1:8787/rhosp13/openstack-neutron-server-ovn:2018-06-19.2 
192.168.24.1:8787/rhosp13/openstack-neutron-metadata-agent-ovn:2018-06-19.2
Comment 16 errata-xmlrpc 2018-06-28 08:00:49 UTC 
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:2085
Note You need to log in before you can comment on or make changes to this bug.