os-net-config

vlans should come up after their device (bond, bridge, etc)

Bug #1453904 reported by Dan Prince
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
os-net-config
Fix Committed
High
Dan Prince

Bug Description

I'm hitting an issue where a VLAN on top of a bridge doesn't work if the bridge isn't already configured first.

The example here doesn't yet work right: https://review.openstack.org/#/c/181999/

The bridges both come up fine... but the VLANs don't because they are started before bond1.

Subsequent runs of os-net-config also don't even try to start the VLAN because the configuration hadn't changed... (perhaps this is a separate bug)

Dan Prince (dan-prince)
Changed in os-net-config:
importance: Undecided → High
status: New → Triaged
Dan Sneddon (dsneddon)
Changed in os-net-config:
assignee: nobody → Dan Sneddon (dsneddon)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to os-net-config (master)

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

Changed in os-net-config:
status: Triaged → In Progress
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Change abandoned on os-net-config (master)

Change abandoned by Dan Sneddon (<email address hidden>) on branch: master
Review: https://review.openstack.org/182023
Reason: This isn't needed for now. We might revisit the interface ordering, but the problem we were trying to solve turned out to have a different solution.

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix proposed to os-net-config (master)

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

Changed in os-net-config:
assignee: Dan Sneddon (dsneddon) → Dan Prince (dan-prince)
Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to os-net-config (master)

Reviewed: https://review.openstack.org/183171
Committed: https://git.openstack.org/cgit/openstack/os-net-config/commit/?id=90f15e38f1e4d80b81f4fa1444dde717917ef8ad
Submitter: Jenkins
Branch: master

commit 90f15e38f1e4d80b81f4fa1444dde717917ef8ad
Author: Dan Prince <email address hidden>
Date: Thu May 14 14:58:10 2015 -0400

    ifcfg: don't set VLAN=yes if is an ovs_port

    When using the ifcfg provider vlans on bridges (or bonds)
    fail to startup correctly. This is because VLANs on an OVS
    bridge are configured as internal ports and these should not
    have the VLAN=yes or PHYSDEV ifcfg settings specified.

    Change-Id: Ieb743eda8f0a25cdaca43bdea767af26bf504f15
    Closes-bug: #1453904

Changed in os-net-config:
status: In Progress → Fix Committed
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.
Subscribing...

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.