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.
DescriptionElyézer Rezende
2016-03-14 19:19:12 UTC
Description of problem:
Version-Release number of selected component (if applicable):
How reproducible:
Always
Steps to Reproduce:
1. Get a system with enp4s0 like named nerwork card
2. run `foreman-installer --scenario capsule ...` enabling dns and dhcp features
Actual results:
The installer tries to find eth0 interface and fail
Expected results:
The installer should identify the default card and not just look for eth0.
Additional info:
[root@sat-capsule ~]# foreman-installer --scenario capsule --parent-fqdn "sat-server.example.com" --register-in-foreman "true" --foreman-base-url "https://sat-server.example.com" --trusted-hosts "sat-server.example.com" --trusted-hosts "sat-capsule.example.com" --oauth-consumer-key "c0n5um3rk3y" --oauth-consumer-secret "c0n5um3r53cr3t" --pulp-oauth-secret "pulp53cr3t" --certs-tar "certs.tar" --dns true --dhcp true
Preparing installation Done
Something went wrong! Check the log for ERROR-level output
The full log is at /var/log/foreman-installer/capsule.log
Relevant log:
[ERROR 2016-03-14 14:46:01 main] Errors encountered during run:
[ERROR 2016-03-14 14:46:01 main] Could not get the ip address from fact ipaddress_eth0 at /usr/share/foreman-installer/modules/foreman_proxy/manifests/proxydhcp.pp:8 on node sat-capsule.example.com
[ERROR 2016-03-14 14:46:01 main] Could not get the ip address from fact ipaddress_eth0 at /usr/share/foreman-installer/modules/foreman_proxy/manifests/proxydhcp.pp:8 on node sat-capsule.example.com
If you're enabling DHCP or DNS, you need to provide the interface name with the appropriate options. See the help for the full set of configuration options for DHCP or DNS.
Currently the default is hard coded as eth0. RFE already in BZ1266090 to guess a better default.
*** This bug has been marked as a duplicate of bug 1266090 ***