Project

General

Profile

Actions

Bug #18252

closed

Foreman uses docker0 ip address as primary interface if docker package is installed

Added by Thomas McKay over 7 years ago. Updated almost 6 years ago.

Status:
Closed
Priority:
Normal
Assignee:
Category:
Importers
Target version:
Difficulty:
Triaged:
Fixed in Releases:
Found in Releases:

Description

Cloned from https://bugzilla.redhat.com/show_bug.cgi?id=1289510

Description of problem:

While provisioning a new host which has docker package installed the primary network interface foreman is using is set to docker0 instead of eth0.

This prevents edit and rebuild operations of this host.

How reproducible:

Provision a new host using a Puppet module or provisioning template to install docker package.

Steps to Reproduce:
1. Provision a host using docker package
2. Go to Hosts -> All Hosts -> Select the host
3. IP Address is set to docker0 IP which is not reachable from Sat6

Actual results:

docker0 IP is set to primary interface

Expected results:

eth0 should be the primary interface used by foreman

Additional info:

As a workaround you can disable update_environment_from_facts: Go to Administer -> Settings -> Puppet and set update_environment_from_facts to False (default: true).


Related issues 1 (1 open0 closed)

Related to Foreman - Bug #17907: bond0 slaves or docker bridges prioritised as primary interfaceNew01/03/2017Actions
Actions

Also available in: Atom PDF