If you deploy, and then reboot, connectivity is lost in controllers

Bug #1656795 reported by Alfredo Moralejo
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Packstack
Undecided
Alfredo Moralejo
puppet-vswitch
Undecided
Alfredo Moralejo

Bug Description

If you set this:

CONFIG_NEUTRON_OVS_BRIDGE_IFACES=br-ex:enp10s0

your external interface will be connected into br-ex (provider network bridge), and neutron now sets the bridge in secure mode.

That means, that after reboot, the flows of such flow will be completely empty, leading to the node being able to communicate with the outside world, compute nodes, etc.

This can be fixed by changing /etc/sysconfig/network-scripts/ifcfg-br-ex

   OVS_EXTRA="set bridge br-ex other-config:hwaddr=8c:89:a5:1a:a8:65"

   to

   OVS_EXTRA="set bridge br-ex other-config:hwaddr=8c:89:a5:1a:a8:65 fail_mode=standalone"

Changed in packstack:
assignee: nobody → Alfredo Moralejo (amoralej)
status: New → Confirmed
Revision history for this message
Alfredo Moralejo (amoralej) wrote :

I've reproduced it.

I think the right place to fix it is in puppet-vswitch, i'm tring to figure out if this new parameter should be always added to OVS bridges or make it optional.

Revision history for this message
Alfredo Moralejo (amoralej) wrote :

Fixed in puppet-vswitch in https://review.openstack.org/#/c/421196/

Changed in puppet-vswitch:
assignee: nobody → Alfredo Moralejo (amoralej)
status: New → Fix Committed
Changed in packstack:
status: Confirmed → Invalid
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/puppet-vswitch 6.2.0

This issue was fixed in the openstack/puppet-vswitch 6.2.0 release.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to puppet-vswitch (stable/newton)

Fix proposed to branch: stable/newton
Review: https://review.openstack.org/435290

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to puppet-vswitch (stable/newton)

Reviewed: https://review.openstack.org/435290
Committed: https://git.openstack.org/cgit/openstack/puppet-vswitch/commit/?id=fc04875852029e70ebd335a1be14e010d59d3a1c
Submitter: Jenkins
Branch: stable/newton

commit fc04875852029e70ebd335a1be14e010d59d3a1c
Author: Alfredo Moralejo <email address hidden>
Date: Tue Jan 17 05:20:46 2017 -0500

    Add fail_mode parameter to OVS Ports

    According to info in https://bugs.launchpad.net/tripleo/+bug/1640812
    when setting a OVS bridge with physical interface we need to
    define fail_mode in OVS_EXTRA parameter of ifcfg to make
    sure it's set at the desired mode after reboot.

    This patch adds new parameter fail_mode to vs_port (as ifcfg is created
    as part of vs_port, not vs_bridge) and defaults it to required value "standalone".

    Similar patch was implemented to os-net-config in
    https://github.com/openstack/os-net-config/commit/e479535b508b4072f64300809b824dfecc3a9182

    Change-Id: I5f7448e3504c9190d7fe5f4a7958c604ef91a058
    Closes-Bug: #1656795
    (cherry picked from commit 026f64ade478a8f3e45a9af61a2239d9ff59acc9)

tags: added: in-stable-newton
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix included in openstack/puppet-vswitch 5.6.0

This issue was fixed in the openstack/puppet-vswitch 5.6.0 release.

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

Other bug subscribers