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.

Bug 1373235

Summary: Installation fails on RHEL 7.2 fully updated
Product: Red Hat Satellite Reporter: German Pulido <gpulido>
Component: InstallationAssignee: satellite6-bugs <satellite6-bugs>
Status: CLOSED WONTFIX QA Contact: Katello QA List <katello-qa-list>
Severity: urgent Docs Contact:
Priority: unspecified    
Version: 6.2.0CC: bbuckingham, gpulido, stbenjam
Target Milestone: Unspecified   
Target Release: Unused   
Hardware: x86_64   
OS: Linux   
Whiteboard:
Fixed In Version: Doc Type: If docs needed, set a value
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-10-13 15:23:02 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 German Pulido 2016-09-05 14:49:01 UTC
Description of problem:
Trying to install most recent Satellite 6 (6.2.1) on a fully updated RHEL 7.2 fails with different errors.

Version-Release number of selected component (if applicable):
Version     : 6.2.1
Release     : 1.3.el7sat


How reproducible:
Always

Steps to Reproduce:
1. Install RHEL 7.2 @Base group
2. Subscribe it to OS repo and update it. Reboot.
3. Subscribe to Satellite repos, and install Satellite packages
4. Install with command line like this:
  # satellite-installer --scenario satellite --foreman-initial-organization "Organization SA" --foreman-initial-location "Location" --foreman-admin-username=satadmin

Actual results:
Install fails:

[root@satellite ~]# satellite-installer --scenario satellite --foreman-initial-organization "Banco de Guayaquil SA" --foreman-initial-location "Guayaquil" --foreman-admin-username=satadmin
 /usr/bin/wget --no-proxy --timeout=30 --tries=40 --wait=20 --retry-connrefused -qO- http://localhost:8080/candlepin/admin/init > /var/log/candlepin/cpinit.log 2>&1 && touch /var/lib/candlepin/cpinit_done returned 4 instead of one of [0]
 /Stage[main]/Candlepin::Service/Exec[cpinit]/returns: change from notrun to 0 failed: /usr/bin/wget --no-proxy --timeout=30 --tries=40 --wait=20 --retry-connrefused -qO- http://localhost:8080/candlepin/admin/init > /var/log/candlepin/cpinit.log 2>&1 && touch /var/lib/candlepin/cpinit_done returned 4 instead of one of [0]
 /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]: Failed to call refresh: /usr/sbin/foreman-rake db:seed returned 1 instead of one of [0]
 /Stage[main]/Foreman::Database/Foreman::Rake[db:seed]/Exec[foreman-rake-db:seed]: /usr/sbin/foreman-rake db:seed returned 1 instead of one of [0]
 /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[satellite.bggrupo.bank]: Failed to call refresh: Proxy satellite.bggrupo.bank cannot be registered (ApipieBindings::MissingArgumentsError: id): N/A
 /Stage[main]/Foreman_proxy::Register/Foreman_smartproxy[satellite.bggrupo.bank]: Proxy satellite.bggrupo.bank cannot be registered (ApipieBindings::MissingArgumentsError: id): N/A
Installing             Done                                               [100%] [..........................................................................................................................................................]
  Something went wrong! Check the log for ERROR-level output
  The full log is at /var/log/foreman-installer/satellite.log
[root@satellite ~]# 

Expected results:
Install goes OK or a meaningful error is thrown

Additional info:

Comment 1 Brad Buckingham 2016-09-06 17:13:08 UTC
Can you attach a foreman-debug that captures the output of the installer failure?  Thanks!

Comment 2 German Pulido 2016-09-07 19:45:20 UTC
Hi

Sorry for the delay. It turns out, this happened because IPv6 was disabled on the server. It is already well documented: https://access.redhat.com/solutions/1605013 however it is a bug (even if it's on an external component, wget) and IMHO it should be fixed.

Thanks!!

Comment 3 Stephen Benjamin 2016-10-13 15:23:02 UTC
Hi, thanks for the bug report.  Not sure we can really do much about this in Satellite.  The underlying cause is IPv6 disabled *and* an IPv6 entry in /etc/hosts.

This is happening in either wget or whatever library it's using to resolve the localhost hostname.

wget or those libraries could be fixed, or users could fix their /etc/hosts.