Note: This bug is displayed in read-only format because
the product is no longer active in Red Hat Bugzilla.
Red Hat Satellite engineering is moving the tracking of its product development work on Satellite to Red Hat Jira (issues.redhat.com). If you're a Red Hat customer, please continue to file support cases via the Red Hat customer portal. If you're not, please head to the "Satellite project" in Red Hat Jira and file new tickets here. Individual Bugzilla bugs will be migrated starting at the end of May. If you cannot log in to RH Jira, please consult article #7032570. That failing, please send an e-mail to the RH Jira admins at rh-issues@redhat.com to troubleshoot your issue as a user management inquiry. The email creates a ServiceNow ticket with Red Hat. Individual Bugzilla bugs that are migrated will be moved to status "CLOSED", resolution "MIGRATED", and set with "MigratedToJIRA" in "Keywords". The link to the successor Jira issue will be found under "Links", have a little "two-footprint" icon next to it, and direct you to the "Satellite project" in Red Hat Jira (issue links are of type "https://issues.redhat.com/browse/SAT-XXXX", where "X" is a digit). This same link will be available in a blue banner at the top of the page informing you that that bug has been migrated.
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).
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?
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.