Project

General

Profile

Actions

Bug #17907

open

bond0 slaves or docker bridges prioritised as primary interface

Added by El Joppa almost 8 years ago. Updated almost 8 years ago.

Status:
New
Priority:
Normal
Assignee:
-
Category:
Network
Target version:
-
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

1.14RC2
Ubuntu 16.04

Chooses bond slave even if it doesnt have ip assigned.
Also chooses docker0 bridge if present.

http://imgur.com/a/hfmrv


Related issues 1 (0 open1 closed)

Related to Foreman - Bug #18252: Foreman uses docker0 ip address as primary interface if docker package is installedClosedThomas McKay01/26/2017Actions
Actions #1

Updated by Anonymous almost 8 years ago

  • Project changed from Smart Proxy to Foreman
Actions #2

Updated by Dominic Cleal almost 8 years ago

  • Subject changed from Foreman prioritizes bond0 slaves or docker bridges as primary interface to bond0 slaves or docker bridges prioritised as primary interface
  • Category set to Network

To clarify, is the host created from a facts import and the bug is in that process?

If you're creating a new host then you select the primary interface using the icons on the left.

Actions #3

Updated by El Joppa almost 8 years ago

Dominic Cleal wrote:

To clarify, is the host created from a facts import and the bug is in that process?

If you're creating a new host then you select the primary interface using the icons on the left.

The host is created from puppet facts import, yes.

Actions #4

Updated by Dominic Cleal almost 8 years ago

  • Related to Bug #18252: Foreman uses docker0 ip address as primary interface if docker package is installed added
Actions #5

Updated by Dominic Cleal almost 8 years ago

Note that the associated bug didn't actually fix the primary interface issue, it only ignores docker* interfaces from being imported. The issue described in both about primary interface selection is unfixed.

Actions

Also available in: Atom PDF