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 917364

Summary: katello-configure: Initializing Katello data fails: rake: Network is unreachable - connect(2)
Product: Red Hat Satellite Reporter: Marcel Wysocki <maci>
Component: InstallationAssignee: Lukas Zapletal <lzap>
Status: CLOSED NOTABUG QA Contact: Katello QA List <katello-qa-list>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 6.0.0CC: lzap
Target Milestone: UnspecifiedKeywords: 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: 2013-03-11 08:23:37 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:
Attachments:
Description Flags
katello-debug after configure none

Description Marcel Wysocki 2013-03-03 15:34:17 UTC
Created attachment 704572 [details]
katello-debug after configure

Description of problem:
katello-configure: Initializing Katello data fails
Fresh installation of Centos 6.3

Version-Release number of selected component (if applicable):
katello-configure-1.2.1-1.el6.noarch

How reproducible:
run katello-configure


Steps to Reproduce:
1.
2.
3.
  
Actual results:
Aborted


Expected results:
Running Katello setup

Comment 2 Lukas Zapletal 2013-03-06 12:34:49 UTC
Marcel,

please read installation instruction carefuly. Did you check you have hostname avaiable through DNS or /etc/hosts?

https://fedorahosted.org/katello/wiki/Install

Can you do

 # ping katello.satgnu.net

to check if this is available? Also check firewall, port 80 and 443 must be open.

https://fedorahosted.org/katello/wiki/FirewallConfiguration

Comment 3 Marcel Wysocki 2013-03-07 13:10:24 UTC
I flushed all iptables rules, set selinux to permissive
also tested to ping my fqdn and shortname, both work fine.

tested 1.1 and 1.2 both seem to be affected

Comment 4 Lukas Zapletal 2013-03-07 15:17:16 UTC
Interesting, would you mind checking out nightly build if this is alredy fixed?

https://fedorahosted.org/katello/wiki/InstallTesting

Comment 5 Marcel Wysocki 2013-03-08 13:41:13 UTC
ok seems to have been some dns issue.
but now i get another problem

[root@katello ~]# katello-configure
Starting Katello configuration
The top-level log file is [/var/log/katello/katello-configure-20130307-231346/main.log]
Creating Katello database user
######################################################################################################################## ... OK
Creating Katello database
######################################################################################################################## ... OK
Creating Candlepin database user
######################################################################################################################## ... OK
err: /Stage[main]/Pulp::Config/Exec[migrate_pulp_db]/returns: change from notrun to 0 failed: pulp-migrate >/var/log/katello/katello-configure/pulp_migrate.log 2>&1 && touch /var/lib/pulp/init.flag returned 1 instead of one of [0] at /usr/share/katello/install/puppet/modules/pulp/manifests/config.pp:60
[root@katello ~]# hostname -d
satgnu.net
[root@katello ~]# hostname -f
katello.satgnu.net
[root@katello ~]# hostname -s
katello
[root@katello ~]# cat /etc/hosts
127.0.0.1   localhost localhost.localdomain localhost4 localhost4.localdomain4
::1         localhost localhost.localdomain localhost6 localhost6.localdomain6
127.0.0.1 katello.satgnu.net katello
::1 katello.satgnu.net katello
[root@katello ~]# ifconfig 
eth0      Link encap:Ethernet  HWaddr 52:54:00:2C:A3:91  
          inet addr:192.168.0.11  Bcast:192.168.0.255  Mask:255.255.255.0
          inet6 addr: fe80::5054:ff:fe2c:a391/64 Scope:Link
          UP BROADCAST RUNNING MULTICAST  MTU:1500  Metric:1
          RX packets:164191 errors:0 dropped:0 overruns:0 frame:0
          TX packets:87807 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:1000 
          RX bytes:167547918 (159.7 MiB)  TX bytes:8042183 (7.6 MiB)

lo        Link encap:Local Loopback  
          inet addr:127.0.0.1  Mask:255.0.0.0
          inet6 addr: ::1/128 Scope:Host
          UP LOOPBACK RUNNING  MTU:16436  Metric:1
          RX packets:307759 errors:0 dropped:0 overruns:0 frame:0
          TX packets:307759 errors:0 dropped:0 overruns:0 carrier:0
          collisions:0 txqueuelen:0 
          RX bytes:75670569 (72.1 MiB)  TX bytes:75670569 (72.1 MiB)

[root@katello ~]# rpm -qa katello
katello-1.2.2-1.el6.noarch

Comment 6 Marcel Wysocki 2013-03-11 08:23:37 UTC
ok, nevermind

i installed a fresh centos 6.4
double checked that the network config is correct.
and installed katello again. tho i got an error about tomcat startup failure during katello-configure i still ended up with a working instance.

sorry for your troubles

Comment 7 Lukas Zapletal 2013-03-13 14:39:19 UTC
Cool, our of curiusity, what DNS issue did you have? Maybe I can add an extra installer check that will verify this...

Comment 8 Marcel Wysocki 2013-03-13 16:17:44 UTC
although the systems FQDN was resolving, it resolved to the wrong ip.
my dns server has a wildmask and i didnt add my katello test system yet.

my katello host first tried to resolv via dns, got an ip and thought it was valid..
thats also why i didnt suspect anything when ping `hostname -f` worked fine, didnt look at the ip too closely



maybe the installer should take nsswitch.conf into account.
or check if the looked up ip matches with an interface definition



also there seem to be problems if the FQDN resolves to 127.0.0.1 and not the external IP