example configs require an IP on the tunnel bridge

Bug #1761715 reported by Jonathan Rosser on 2018-04-06
10
This bug affects 2 people
Affects Status Importance Assigned to Milestone
openstack-ansible
Undecided
Jonathan Rosser

Bug Description

Now that the default is to deploy the l3 agent on bare metal the deployer must assign an IP to br-vxlan for the deploy to be functional. This is not shown in the "IP assignments" table.

This applies to all of the examples.

Fix proposed to branch: master
Review: https://review.openstack.org/559775

Changed in openstack-ansible:
assignee: nobody → Jonathan Rosser (jrosser)
status: New → In Progress

Reviewed: https://review.openstack.org/559775
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=55e8240b86e5b14c9b2bd78e29a207a0c2bb0d6f
Submitter: Zuul
Branch: master

commit 55e8240b86e5b14c9b2bd78e29a207a0c2bb0d6f
Author: Jonathan Rosser <email address hidden>
Date: Mon Apr 9 15:49:28 2018 +0000

    Add IP addresses to infra node br-vxlan in the examples

    The layer 3 agent is no longer containerised by default so the bare
    metal host requires an IP to be assigned to br-vxlan

    Change-Id: If3e1511546c6192f11ef1702d09772643b4fe9b7
    Closes-Bug: #1761715

Changed in openstack-ansible:
status: In Progress → Fix Released

Reviewed: https://review.openstack.org/562329
Committed: https://git.openstack.org/cgit/openstack/openstack-ansible/commit/?id=782285bb56bde4d649f4f699680d163783a1e056
Submitter: Zuul
Branch: stable/queens

commit 782285bb56bde4d649f4f699680d163783a1e056
Author: Jonathan Rosser <email address hidden>
Date: Mon Apr 9 15:49:28 2018 +0000

    Add IP addresses to infra node br-vxlan in the examples

    The layer 3 agent is no longer containerised by default so the bare
    metal host requires an IP to be assigned to br-vxlan

    Change-Id: If3e1511546c6192f11ef1702d09772643b4fe9b7
    Closes-Bug: #1761715
    (cherry picked from commit 55e8240b86e5b14c9b2bd78e29a207a0c2bb0d6f)

tags: added: in-stable-queens

This issue was fixed in the openstack/openstack-ansible 17.0.3 release.

This issue was fixed in the openstack/openstack-ansible 18.0.0.0b1 development milestone.

This issue was fixed in the openstack/openstack-ansible 18.0.0.0b2 development milestone.

To post a comment you must log in.
This report contains Public information  Edit
Everyone can see this information.

Other bug subscribers