os-net-config

  1. Bug #1806027
  2. Comment #5

Comment 5 for bug 1806027

Revision history for this message
OpenStack Infra (hudson-openstack) wrote : Fix merged to os-net-config (stable/pike)

Reviewed: https://review.openstack.org/621989
Committed: https://git.openstack.org/cgit/openstack/os-net-config/commit/?id=2f6f6cb6ab190cf8c7bbe5c113d8279863cfff03
Submitter: Zuul
Branch: stable/pike

commit 2f6f6cb6ab190cf8c7bbe5c113d8279863cfff03
Author: Harald Jensås <email address hidden>
Date: Fri Nov 30 10:54:06 2018 +0100

    Fix - restart VLAN interface on underlying device change

    When a change is needed on bond, os-net-config write the
    configuration and restart nic and bond. But it does not
    restart vlan on top of the bond. The results is that all
    routes for vlan interfaces are lost.

    This moves the processing of VLAN's so that it run's
    after any interfaces, bridges, bonds etc. Then
    concatenates the restart lists from other interfaces and
    do a check if 'PHYSDEV' of a VLAN interface is being
    restarted.

    Closes-Bug: #1806027
    Related: RHBZ#1654987
    Change-Id: I246da54cf02d06466f52d210f89d82ca9e2a6ef2
    (cherry picked from commit 19067b4e77ec618ffef67acc771869ecbc33ad34)