Feature #21104

Recognize br-ex, br-int and br-tun as bridge interfaces

Added by Christian Schulze-Wiehenbrauk 7 months ago. Updated 7 months ago.

Status:Closed
Priority:Normal
Assigned To:-
Category:-
Target version:-
Difficulty:trivial Bugzilla link:
Found in release:1.15.1 Pull request:https://github.com/theforeman/foreman/pull/4872
Story points-
Velocity based estimate-
Release1.16.0Release relationshipAuto

Description

In the openstack dvr configuration scenario, bridges would be created on compute and network nodes called br-tun, br-ex, br-int and br-vlan. Unfortunately foreman does not recognize these devices as bridges, since the regex pattern matches only "br" + number (for that case).

This brings the unfortunate side effect, that the interfaces on which this bridges are created might vanish, because facter might report these with the same mac as the interfaces they were created on.

As this bridge naming pattern is quasi standard for some specific openstack configurations, it would be great if foreman would accept the "br-(\w)" pattern.

Implementation change would be required here:
https://github.com/theforeman/foreman/blob/develop/app/services/fact_parser.rb#L4

Associated revisions

Revision bc03373f
Added by Christian 7 months ago

Fixes #21104 - Recognize br-ex etc as bridge interfaces

Extends the bridge regex pattern to allow bridges named after purpose
like br-ex, br-tun as documented in openstack dvr scenario.

History

#1 Updated by The Foreman Bot 7 months ago

  • Status changed from New to Ready For Testing
  • Pull request https://github.com/theforeman/foreman/pull/4872 added

#2 Updated by Anonymous 7 months ago

  • Status changed from Ready For Testing to Closed
  • % Done changed from 0 to 100

#3 Updated by Daniel Lobato Garcia 7 months ago

  • Release set to 1.16.0

Also available in: Atom PDF