Bug 1289510

Summary:	Foreman uses docker0 ip address as primary interface if docker package is installed
Product:	Red Hat Satellite	Reporter:	Dirk Herrmann <dherrman>
Component:	Provisioning	Assignee:	Tom McKay <tomckay>
Status:	CLOSED NEXTRELEASE	QA Contact:	Katello QA List <katello-qa-list>
Severity:	low	Docs Contact:
Priority:	unspecified
Version:	6.2.0	CC:	egolov, ehelms, inecas, jcallaha, jyejare, mburgerh, tomckay
Target Milestone:	Unspecified	Keywords:	Triaged
Target Release:	Unused
Hardware:	Unspecified
OS:	Unspecified
Whiteboard:
Fixed In Version:		Doc Type:	Bug Fix
Doc Text:		Story Points:	---
Clone Of:		Environment:
Last Closed:	2017-08-01 19:57:58 UTC	Type:	Bug
Regression:	---	Mount Type:	---
Documentation:	---	CRM:
Verified Versions:		Category:	---
oVirt Team:	---	RHEL 7.3 requirements from Atomic Host:
Cloudforms Team:	---	Target Upstream Version:
Embargoed:

Description Dirk Herrmann 2015-12-08 11:31:31 UTC

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.

Version-Release number of selected component (if applicable):

Tested with Satellite 6.1.2,3,4.

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).

Comment 1 Maxim Burgerhout 2016-04-29 10:17:02 UTC

SAtellite 6.2 has a configurable list of interfaces that are to be ignored. The docker0 interface isn't part of that list out of the box, but it would make sense to include it there by default.

Settings -> Provisioning -> Ignore interfaces with matching identifier

As we now include the possibility to install Atomic hosts from Satellite, this becomes more important imo

Makes sense to change component to Provisioning?

Comment 2 Bryan Kearney 2016-07-26 19:09:04 UTC

Moving 6.2 bugs out to sat-backlog.

Comment 3 Tom McKay 2017-01-26 13:42:42 UTC

Created redmine issue http://projects.theforeman.org/issues/18252 from this bug

Comment 4 Satellite Program 2017-01-26 15:19:32 UTC

Upstream bug assigned to tomckay

Comment 5 Satellite Program 2017-01-26 15:19:35 UTC

Upstream bug assigned to tomckay

Comment 6 Satellite Program 2017-01-26 21:19:41 UTC

Moving this bug to POST for triage into Satellite 6 since the upstream issue http://projects.theforeman.org/issues/18252 has been resolved.

Comment 8 Evgeni Golov 2017-05-30 10:12:06 UTC

FWIW, You can manually apply the fix from the upstream PR (https://github.com/theforeman/foreman/pull/4233) by adding "docker*" to "ignored_interface_identifiers" in the settings of Satellite.

Comment 9 Sachin Ghai 2017-05-30 11:33:30 UTC

*** Bug 1445692 has been marked as a duplicate of this bug. ***

Comment 10 Bryan Kearney 2017-08-01 19:57:58 UTC

The fix to this bug will be delivered with release 6.3 of Satellite.