NIC no more belongs to bridges after server reboot

Bug #1531895 reported by Alexander Rubtsov on 2016-01-07
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Fuel for OpenStack
slava valyavskiy

Bug Description

MOS: 7.0
Feature: Reduced footprint

Virtual machines (which are hosted by a node with "virt" role) lose their network configuration after reboot
If we use 1 NIC for mapping of all logical networks (without bondings), after reboot this NIC will disappear from bridges (which it is supposed to be in)

To make this settings permanent, the corresponding configuration files, in the /etc/network/interfaces.d/ directory, should be configured according to the specifications:

For example:
auto eth2
iface eth2 inet manual
ovs_bridge br-fw-admin
ovs_type OVSPort

Alexander Rubtsov (arubtsov) wrote :

sla2 for 7.0-updates

tags: added: sla2
Artem Roma (aroma-x) on 2016-01-08
tags: added: area-library
Changed in fuel:
assignee: nobody → Fuel Library Team (fuel-library)
milestone: none → 7.0-updates
importance: Undecided → High
status: New → Confirmed
Bogdan Dobrelya (bogdando) wrote :

Please note that according to the design spec, the VMs are "fire and forget". There was healing/monitoring by design

Changed in fuel:
status: Confirmed → Won't Fix
Anton Matveev (amatveev) on 2016-01-11
tags: added: feature-reduced-footprint
Alexander Rubtsov (arubtsov) wrote :

From the feature specification:
"Virtual machines will be treated by Fuel as standard bare metal servers. Fuel will allow only to start/deploy VMs. User should take care about VMs maintenance. We will deliver fire-and-forget solution"

I think that making NIC a permanent part of the corresponding bridge is related to proper network configuration rather than maintenance

Currently, use cases that include hosts reboot are blocked and require manual reconfiguration
Could you please revise the implementation?

Bogdan Dobrelya (bogdando) wrote :

Yes, I believe the decision should be to drop this experimental feature as a set of bash scripts and reimplement it from the scratch but using Nova API to spawn and LCM instances

Changed in fuel:
status: Won't Fix → Invalid
status: Invalid → Incomplete
Changed in fuel:
assignee: Fuel Library Team (fuel-library) → slava valyavskiy (slava-val-al)
slava valyavskiy (slava-val-al) wrote :

I have checked the following case:
1. I have used network template
2. I have used ovs provider for br-fw-admin
3. I have connected physical interface directly into br-fw-admin bridge

As result of application netconfig task I get appropriate network configuration is in place.

root@node-3:~# cat /etc/network/interfaces.d/ifcfg-br-fw-admin
auto br-fw-admin
allow-ovs br-fw-admin
iface br-fw-admin inet static
ovs_ports eth0
ovs_type OVSBridge

slava valyavskiy (slava-val-al) wrote :

I'm checking ovs-to-ovs network configuration. Right now, I guess this bug is duplication of

slava valyavskiy (slava-val-al) wrote :

I was able to reproduce issue for following network configuration(part of network template):
        - action: add-br
          name: br-fw-admin
          provider: ovs
        - action: add-br
          name: br-mgmt
          provider: ovs
        - action: add-patch
          - br-fw-admin
          - br-mgmt
          mtu: 9000
          provider: ovs
          - 100
          - 0
        - action: add-port
          bridge: br-fw-admin
          name: <% if1 %>

summary: - [Reduced footprint] NIC no more belongs to bridges after server reboot
+ NIC no more belongs to bridges after server reboot
tags: removed: feature-reduced-footprint
tags: added: l23network
slava valyavskiy (slava-val-al) wrote :

It seems that approach described in bug's description is correct. Currently, l23network generates following configuration for physical ports:
root@node-3:~# cat ifcfg-eth0
auto eth0
iface eth0 inet manual

but, it should look like(works for me):
root@node-3:~# cat /etc/network/interfaces.d/ifcfg-eth0
allow-br-fw-admin eth0
iface eth0 inet manual
ovs_type OVSPort
ovs_bridge br-fw-admin

Changed in fuel:
status: Incomplete → Confirmed

It seems that l23 network module should be fixed to handle specific type of port for ovs provider:
        - action: add-port
          bridge: br-fw-admin
          name: <% if1 %>
          provider: ovs

Anton Matveev (amatveev) on 2016-01-13
tags: added: sla1
removed: sla2
Anton Matveev (amatveev) wrote :

sla1 for MOS7.0

Change abandoned by Valyavskiy Viacheslav (<email address hidden>) on branch: stable/7.0

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

Other bug subscribers